Question About Error Message

[Guest]

Hi,

I just tried to enter a database that I am working on and received this
message:

The database has been placed in a state by user "Admin' on machine
'ANN-MARIE' that prevents it from being opened or locked."

What causes this user to lock everyone else out of the database when she is
in it?

 

[Matt]

Hi,

I just tried to enter a database that I am working on and received this
message:

The database has been placed in a state by user "Admin' on machine
'ANN-MARIE' that prevents it from being opened or locked."

What causes this user to lock everyone else out of the database when she is
in it?

Does is lock you out totally or just from making changes?

 

[Guest]

It locks me totally out, though there are other occasions where I can view
Read Only. This one won't even let me open the database.

 

[Guest]

Hi Novice,

It could be that her settings are automatically locking everyone else out.
To check it the database would have to be opened from her machine. On the
Menu Bar click Toos then select Options. Next, select the Advanced tab.
Look under "Default Record Locking" and if "All Records" is selected change
it to Edited Records.

Hope that helps.

Hunter57
Just huntin' for the right data.
http://churchmanagementsoftware.googlepages.com

 

[Scott McDaniel]

Hi,

I just tried to enter a database that I am working on and received this
message:

The database has been placed in a state by user "Admin' on machine
'ANN-MARIE' that prevents it from being opened or locked."

What causes this user to lock everyone else out of the database when she is
in it?

The user on the ANN-MARIE machine could have the database opened in Exclusive mode. Check with that user to make sure
they're not doing so.

Is this application split? If so, are users sharing the SAME frontend? Generally this is a bad idea, and all users
should have their own copy of the frontend, and each of those copies would connect (i.e. "link") to the same copy of the
backend.

If not split, then perhaps the user on ANN-MARIE has opened an object in Design view. This can lock everyone else out of
the db, especially if they're mucking around in tables.

If the database is NOT split, then you'd be well advised to do so if you're going to support multiple users.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

 

[Guest]

Good point. I doubt if they have their own front end. I inherited this.
Mucking about in the table is what everyone is doing now. I at least hoped to
give them a form to use, if I can get them to use it.

How would one go about creating a "front end" for each user?

 

[Matt]

Good point. I doubt if they have their own front end. I inherited this.
Mucking about in the table is what everyone is doing now. I at least hoped to
give them a form to use, if I can get them to use it.

How would one go about creating a "front end" for each user?








- Show quoted text -

All you need to do is copy the frontend from the server on to the
users machine ... each user should have the same exact copy of the
database on the server (Still linked to the backend).

 

[John W. Vinson]

Good point. I doubt if they have their own front end. I inherited this.
Mucking about in the table is what everyone is doing now. I at least hoped to
give them a form to use, if I can get them to use it.

How would one go about creating a "front end" for each user?

Tools... Database Utilities... Database Spliter Wizard.

This will put all the Tables into a file with _BE appended to the filename.
That should be on a shared drive, and each user should get their own copy of
the frontend (which will have the same name as the original database).

John W. Vinson [MVP]