Question The database has been placed in a state by user “Admin” on machine

A

Amruta

New member
Local time
Yesterday, 16:39
Joined
Sep 9, 2010
Messages
6
I have this unique problem popping up at out organization with has Access database and forms.
There is is this one computer which has Ms Access 2007 installed on it and the rest of the three pc's have access 2003 installed on it.
We have this one database on the shared network which all of these pc's can access. But there is one catch: If the pc with MsAccess 2007 opens the database first then no other pc can open the database after that giving out the error as "The database has been placed in a state by user “Admin” on machine that prevents it from being opened or locked". However if the pc's with access 2003 opens the database first then everyone CAN open the database after that (including the one which has access 2007 on it). So I really don't know what the exact problem is. Can anybody please help me out on this??? Will appreciate any help on this.
 
Okay, this is a common theme amongst people sometimes.

1. The database should be split (frontend and backend - backend has tables only).

2. EACH USER should have a copy of the frontend on THEIR MACHINE. You should not be opening the same file by each user.

3. And it is worse when you start mixing versions and opening the same file.

So the fix is - Split it, if it isn't and give each user a copy of the frontend on their machine.
 
thanks boblarson
 
Also has anybody heard about this strange error "Reserved error -5500there is no message for error"
This happens only when the users have the database open and are away from the computer for like 20-25 min and then when they come back again the database hangs giving out the above error. Does anybody know more about this error and why does it happen?
 
You might be suffering from dropped network connections. That is possible. It doesn't have to drop for a long time, but just a little can do it. That can also cause corruption (another reason why the split is important, as it will likely kill the frontend copy before it does anything to the data copy. It can corrupt the data potentially but it is much less likely).

Also, do you have any timer events going on anywhere?
 
By timer events , do you mean timer events in the database?
 
boblarson said:
Okay, this is a common theme amongst people sometimes.

1. The database should be split (frontend and backend - backend has tables only).

2. EACH USER should have a copy of the frontend on THEIR MACHINE. You should not be opening the same file by each user.

3. And it is worse when you start mixing versions and opening the same file.

So the fix is - Split it, if it isn't and give each user a copy of the frontend on their machine.
Click to expand...

I am dealing with a situation with this same error....but in Access 2010. I can't seem to find a way to get the database to open in shared mode. Even without placing anything in edit mode, we get this error. The database is on a network folder. I looked how to split the database as you advise, but it brings up a big issue for me...... how do you propagate changes that effect the front end (ie - changes to the forms or reports).

I am missing something (probably!) with how the front end vs. back end splitting works?
 
LisaRae007 said:
how do you propagate changes that effect the front end (ie - changes to the forms or reports).
Click to expand...
You can use my free tool to enable auto updating on the frontend if you wish. That way you can work on your master frontend copy and then when it is ready to deploy to the users you would just change the version number in the frontend and backend tables. The frontend when opened by the user then checks to see if it matches with the version listed in the backend and if it doesn't, it tells the user that their frontend is out of date, closes itself, deletes itself, copies the new version down from your master location, and then automatically reopens for them. The only time you have to worry about deployment is the initial deployment. From then on, the frontend Auto Updating does the work.

Go here for my free Frontend Auto Update Enabling tool:
http://www.btabdevelopment.com/ts/freetools

I am missing something (probably!) with how the front end vs. back end splitting works?
Click to expand...

The splitting is that the backend retains the data. The frontend copy is linked to the backend and then deployed to each user. They are all connected to the same data but run on the machine that the user is on. This not only limits the possible corruption that can occur but also limits the type of collisions that can occur when running the same exact database file from multiple users.
 
I have the same problem with 2010 except that I'm opening it up as a single user on a local machine. It's a sporadic problem whenever I try to open the database file in VBA.
 
oneillj said:
I have the same problem with 2010 except that I'm opening it up as a single user on a local machine. It's a sporadic problem whenever I try to open the database file in VBA.
Click to expand...

oneillj: your problem is most likely due to not using CurrentProject.Connection if using ADO for the connection object (don't use a connection which puts in the path of the database), or if using DAO, you haven't used
Set db = CurrentDb
and instead use another way to connect, again using a path to the database.
 
You must log in or register to reply here.

Similar threads

P
No Options in File - Access Runtime 2021
Replies
10
Views
541
Pat Hartman
P
B
Advice Request : Simplest method to allow multi-site access to a prototype database
Replies
10
Views
532
Pat Hartman
P
A
Solved Access Database Locking Issue
2
Replies
31
Views
1,571
Ajay289
A
oxicottin
Solved Need help with a new user that can't enter data
Replies
14
Views
600
gemma-the-husky
gemma-the-husky
B
Pop up forms not "stacking" in the right order
Replies
12
Views
426
CJ_London
C

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top Bottom