Re: "you and another user..."--standard fixes don't apply
- From: Jan <jan@xxxxxxxxxxxxxx>
- Date: Thu, 28 Aug 2008 17:50:04 -0500
Hi, Salad:
I know exactly where it happens, and it happens to most if not all the users, not just one.
It happens in a routine (actually, a function) that writes the record back to the server, from the temp tables. It's called mostly during after_update, but sometimes in other places. I've seen the code break point, and I still don't know what's causing the error. They are using the full version, not runtime.
In my Google search on this error, some pointed to page locking issues. I don't see why this would be a problem as the update is done with a recordset, so the record isn't open for very long.
Other question/ideas?
Salad wrote:
Jan wrote:....
Hi:
....It generally happens on one particular subform, but sometimes happens on another one. I believe it happens at the point at which the record is written back to the main db on the server (from the local temp tables). The client is in California and I'm in Chicago so I can't watch them work. They won't give me the ability to log onto their individual workstations to troubleshoot. I can't reproduce the problem, either on my computer here, or on the computer to which I do have remote access.
I have searched this problem and looked at all the proposed causes, and none of them applies.
There are no Memo fields.
I have compacted, rebuilt the tables, written all data to new tables on a clean blank database, I believe there is no data corruption.
This error occurs intermittently. They can go a few days with no errors but then have them on every two or three records for a few days.
I believe that most of the clerks get the errors but that some don't, or some get them less often.
Do you have any code, main or subform, that in the form's AfterUpdate it updates any tables or runs an action query?.
Is it a specific person that gets the problem? It may be something they do that you aren't trapping for...as in you might test it a certain way but the user does something differently or the user enters something differently than you.
Do you have any idea when the error occurs? What line of code, what event triggers the problem?
Are they running a full version of Access and not a runtime? You could search for On Err and replace with 'On Err for the problem forms code (don't do that on On Error Resume Next or On Error GoTo 0's) so the code can get into Debug?
In your error message do you have the routine it breaks on. Ex:
Msgbox Err.Description,,"Form_AfterUpdate"
so you get an idea where the message is coming from?
- References:
- Prev by Date: Re: Forcing users to save exported reports to a specific folder
- Next by Date: Comparing Difference (in Years) Between Two Dates & Totalling - Troubleshooting
- Previous by thread: Re: "you and another user..."--standard fixes don't apply
- Next by thread: Re: "you and another user..."--standard fixes don't apply
- Index(es):
Relevant Pages
|