|
Subject:
|
Incorrect Error Message Claims Multiple Users
|
|
Posted By:
|
SerranoG
|
Post Date:
|
4/21/2005 1:26:23 PM
|
I have a small Access XP database with a main table (has a PK) and other tables that have FKs to it. The form is bound to the main table and its subforms are inside tabs which have a parent/child relationship to the main form.
Every now and then, the data input person gets this message:
"The Microsoft Jet database engine stopped the process because you and another user are attempting to change data at the same time."
This is simply not true. She's the only one on it even though the MDB is on the network.
When she clicks OK, the message continues to appear until all the textboxes on the subform display #Error. If she goes to another record and comes back, the data for those wacky records (form and subform) are still intact.
Any ideas of what causes that? Thanks in advance. 
Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division
|
|
Reply By:
|
SerranoG
|
Reply Date:
|
4/25/2005 10:00:40 AM
|
I'm trying to track what triggers the behavior. Here's what I've noticed. When I enter a new record in the subform the first time, everything is OK. When I go to a new record on the main form and then enter the subform to add its details, I get the error about someone else having the database open. It's that second time. It's as though Access thinks I still have that previous record open for editing and a second person is now trying to edit it.
If the main form goes to a new record, the subform is linked to it via master/child of the primary/foreign key. The subform should be sitting there at a new record as well, but the error message is telling me it's still on the previous record even though the subform is blank.
Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division
|
|
Reply By:
|
rjweers
|
Reply Date:
|
4/26/2005 8:03:00 AM
|
This one seems odd. You could check to see if the query of the master form includes a field from one of the tables in the subform or vice versa. If you add a new master, it's going to try to add the associated record in the subform table. Normally, the new record should be created in the subform as soon as someone starts typing.
If the subform is trying to update a field in the master's tables, updates in the subform will have updated the master form's tables while you're in the subform. Going back to the master form and going to a new record will try to update the master's tables again.
Also check to see if you have any code that would update a field on the master from the subform.
Randall J Weers
Membership Vice President
Pacific NorthWest Access Developers Group
http://www.pnwadg.org
|
|
Reply By:
|
SerranoG
|
Reply Date:
|
4/27/2005 1:11:13 PM
|
I did extensive checking and did not find the main/subform trying to update records on the sub/main form upon opening. As a wild hunch, I went to the subform's design view and reset its CYCLE property from CURRENT RECORD to ALL RECORDS.
So far, that seems to have done the trick; but why restricting cycling in the subform to one record would trigger that error is odd! If it comes back, I'll let you know.
Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division
|
