Designing the database while other users have it open

G

GD

I am tyring to modify a database (Access 2000) that is
being used in my dept. I need to add new forms, tables,
queries, reports, etc. My problem is that if other users
have the database open, it is not allowing me to add these
changes. When another user has the database open, I get a
message that says that I do not have exclusive access to
the database at this time, and that my design changes will
not be saved.

The database is located on a server and there are about 6
different people located in 2 seperate buildings that are
using this database.

I didn't have an trouble like this when using a previous
version of access. I am new to Access 2000 and don't know
how to rectify this problem. This database is used
constantly throughout the day by all 6 people and it will
be nearly impossible to not let any of them use it while I
am trying to update the design.

Are there any solutions that will allow me to work on the
development of the database while others have it open as
well?

Thank you in advance for any help that you can give me.
GD
 
A

Arvin Meyer

The save model change to a monolithic save, beginning with Access 2000.

First split your database, if you haven't already done so, into a front-end
(forms, queries, code, reports) and the data (tables) on the server. Now you
can work on a copy of the front-end without interruption. You can use a
versioning utility, like the free one on my website:

http://www.datastrat.com/Download/Starter.zip

to have the users get the copy of the changed file as they log in.

The back-end changes you need to make before or after anyone else logs in.
Since there are fewer of them and you can import or copy/paste them, the
interruptions should be minimum.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
P

Paul Overway

You cannot do this. Access 97 allowed it, but it often caused corruption of
the database. You need to make a copy of the database, modify THAT, then
replace the original database once you are satisfied that the modifications
work properly.
 
Top