Is there any way to make design changes when multiple users are in? 1

[BTilson]

Quite a few of the applications I have developed over time are used in a multi user environment, quite often with multiple users logged in and using the database at once. This can be rather annoying when I need to make a quick change to something in the DB. Access warns me that I do not have exclusive access to the DB and that any design changes may not be saved. I'm not sure why they even say "may", as I've never had it allow me to save changes when anyone besides myself was in the database.

This situation causes me to have to run all over the plant to every station hunting for computers that might have my app open. So I wind up spending half an hour checking computers just so I can make a 10 second code change.

Does anyone know if there is any way around this, or am I just stuck with the way it is?

Thanks in advance!

Brooks Tilson
Database Development
Tilson Machine, Inc.

 

[Remou]

The usual way is to make changes to a 'master' front-end and have it upload the various workstations at an appropriate time.

There are FAQs; here is one that a very quick search turned up:

http://www.tek-tips.com/faqs.cfm?fid=5062

 

[BTilson]

That should work, but given the current setup (one file on the server that everyone just opens from their workstation) there is no way to get around my problem?

Thanks you, by the way.

Brooks Tilson
Database Development
Tilson Machine, Inc.

 

[Remou]

No. It is not a set-up that is recommended:

http://msdn.microsoft.com/en-us/library/aa167840.aspx

 

[fneily]

At one school I set up a single copy of the database, their network admin. set up a broadcast message to all users to save and log off in 10 minutes or the users will just be dropped.

 

[JoeAtWork]

Most of my multi-user set ups have their shortcut pointing to a batch file rather than the MDB itself. The batch file copies the MDB front-end to their local temp directory, and then opens it from there. Advantages:

1. Everyone has their own local copy of the front-end, which usually runs better than sharing a network copy
2. Everyone gets a pristine version of the MDB each time they start
3. Can distribute new version just by copying to the network share

This of course assumes you have split the database to front-end/back-end versions. If you have not done that, then do so ASAP, as you are otherwise risking corrupting the data.

 

[BTilson]

Hey, I really like the batch file idea. But unfortunately, none of my db's are currently split up. I will look into getting that done asap, and using your batch file idea.

Thanks!

Brooks Tilson
Database Development
Tilson Machine, Inc.