Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Multi-User Problem

Multi-User Problem

Multi-User Problem

I'm getting error 3734 (The database has been placed in a state by user 'Admin' on 'SOLS-DC1' that prevents it from being opened or locked.) when two or more users attempt to simultaneously insert records into the same table in the backend database. Sometimes it's error -2147467259 with the same err description. This is a split design with a central mdb that accessed from distributed mde applications. Each user has their own copy of the mde. The Access version is 2002. I can reproduce this error 100% in a test environment. All users have been granted "full control" security permissions in the backend database folder. The mde files have links to the tables in the backend that they use. I have tried using ADO and DAO for the record inserts and get the same result. The code that is causing the problem is a simple loop through a recordset that builds an SQL string for the record insert and executes it each loop through. I'm thinking that this is some sort of .ldb file creation/closure that can't keep up with the access attempts. Does anyoue out there have experience with this problem?

RE: Multi-User Problem


I've never experienced your problem (not that I can remember anyway), but that's probably because I never open / close a database multiple times, rapidly.
I never do that for performance reasons more than anything.
Even if the logic 'forced' me to do it that way - I'd find a way to open the db once, read / write to it multiple times then close it - once (it is common / advised practice)

Is there a reason that you must open the db WITHIN the write loop?
Can it not be opened / closed OUTSIDE the loop?
If not, then you'd have to trap the error, then wait until it cleared before the next write.

If you can't think of a solution, paste your loop code in here.



Never argue with an idiot, he'll bring you down to his level - then beat you with experience.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close