Access 2000 Shared Database

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

I'm hoping someone can help me out here. I'm having a
problem with a shared database. I have to seperate db's
setup, one called data and one called apps. Apps is where
all the forms, queries, reports, etc... are located and
the tables are linked back to data.

The error message I get is:

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

Now, I get this message when a user has the database open
and is making changes to the design of a form or report.
When no one is making changes I can open it without any
problems what so ever.

I have the users settings set at record-locking, shared
access, and lock edited record only. Any ideas would for
things to try would be greatly appreciated.

Thanks,

Jason
 
Hi, Jason.

This behavior is by design. In Access 2K and later versions, a user must
have exclusive access to the file when making changes to database
application objects, such as Forms, Reports, and Modules, due to the
monolithic architecture of these objects. All of these objects are saved in
one record, so if a user saves the changes to a Form while another user is
in the database using any of the other database application objects, the
database would very likely become corrupted. Access 97 and earlier versions
didn't have this built-in safeguard, and are much more likely to become
corrupted while saving changes in a multiuser database.

In a multiuser environment, the data objects (tables and their
relationships) are located in an MDB file on the network shared directory,
while the database application objects are located in a front end database
file. The best scenario (i.e., least corruption, best performance, easiest
maintenance) is to have a copy of the front end on each database user's
workstation, not on a network shared directory. Whenever updates to the
database application objects are needed, the new front end is distributed
automatically to the workstations. Try out Tony Toews' Auto FE Updater
utility to see how smoothly this can go when done correctly. See the
following Web page:

http://www.granite.ab.ca/access/autofe.htm

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Thanks, that does help. That was the answer I was afraid
I was going to receive, but oh well. Thanks for the link,
I'll check it out.

Jason
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top