The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time.

ERROR: The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time.

I have a service tracking DB which is divided into 2 sections customer data which is pulled from linked SQL tables and is not editable and repair data which the user enters. I am getting the above error when more than one user is entering data into the Repair Information section which consists of 2 sub forms, I have changed the Record Locks property to Edited Record on all forms but still get the error, and I have also repaired and compacted the DB. The error does not appear if only one user is entering data. Any suggestions would be greatly appreciated. I have included a screen shot of the form.

ATIService01-Jul.-06-12.16.jpg
skull52IT director Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ErezMorCommented:
first, change it back to NoLocks, cause that's even more loose locking logic
second, are the 2 users using the same front mdb file or do they have seperate copies of it?
if not, then start by giving each user his own copy of the mdb, and if the tables are local, then split the mdb file first (there's a wizard for database splitting) to a back end and fron end, then have the users run a seperate copy of the front end (you will need the linked table to sql on the front end)
 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
skull52IT director Author Commented:
OK,
I changed the Record Locks property back to No Locks, split the database and gave each user their own copy, still I get the error whenever user 1 attempts to enter data even if user 2 only has the DB open and not entering data
0
ErezMorCommented:
let me get it straight. user 2 only opened the mdb file (the above form is not opened) and still user1 gets that error when entering data into the subform?
if user1 enters data in the same place and user2 is not inside the db everything works?
i must say this is indeed strange, and i never encountered anything like it.
if that is so then i'm afraid i cant figure out a solution without the mdb file itself (i'll be ok without the actual data from sqlServer, but the back end will be helpful)
in bizzare cases such as this i make a copy of the problematic form, then start disecting it (running both users with a form with no subfom, then running both users with only the subforms opened directly...
it's not fun, but it eventually does bring results
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

puppydogbuddyCommented:
Here are two things you should check for because either will cause locking conflicts:
        1.  Database should be set to open in "Shared Mode".     Tools>Options>Advanced tab
        2.  Check if the application is running any action queries (inserts, deletes, updates)  at the same time your users are entering data on the form that effect the same tables.
0
puppydogbuddyCommented:
<<<<if user1 enters data in the same place and user2 is not inside the db everything works?>>>
Assuming the forms are bound, this could indicate that there are changes entered on form1 by user1 that were not saved at the time User2 tried to save form changes affecting one or more records on the same record page as User1.
0
Bill RossProgrammerCommented:
In my history this is a corrupt record in the Repair table.  It is not a form issue.  Open the repair table in a db directly.  Create a make table query that creates a local table using just the repair table as it's source.  Run the query and see if you get the message.  If so - let me know and I'll help you repair it.
0
skull52IT director Author Commented:
Thanks for all your help,  but the problem stemmed from one user using the edit parts table form as a look-up. That table is used to populated the parts used subform, so when he opened the form and tried to add the part it errored.
0
skull52IT director Author Commented:
ErezMor suggestion to split the database was a good one even though it did not fix the problem so I am awarding him the lions share of the point and splitting the rest among everyone else as they were good suggestions
0
ErezMorCommented:
cheers mate!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.