Safest way to working on live databases

[pat_nospam]

I want to make form updates and database modifications, what is the best way to accomplish this with a live database. If I have a production copy and a live copy, how do I swap the two when they are "Secured" with the Users and Groups permissions (i.e. Secured.mdw and a shortcut to open).

Thanks in advance

 

[Autoeng]

I use a event to lock the users out of the db to make changes. Do a search on "log users off" and posted by Autoeng.

 

[Autoeng]

Also you should be working on a "working" copy of the db and then overwrite the "user" copy when the changes are how you wnat them.

 

[pat_nospam]

How do I accomplish this with a secured database (shortcut points to secured.mdw)?

BTW - thanks for all your help yesterday. I ended up going with the Microsoft solution because it was 2002 compliant without the DAO installations. It does the same trick, and is only dependent on an external file rather than an external table/database.

Thanks again

 

[Autoeng]

You will need to split the db into front end (FE) and backend (BE). BE is on a server and users utilize a batch file to download the FE to their PC. You work on form design on the FE copy of your PC. If you need to add fields to BE tables use your code to close the db to kick the users out and work on the BE on the server. Changes made to your working copy FE can just be copied to the server location so that the next time a user runs the batch file they get the latest copy. I did a lot of work with another forum user on distributed db's here... http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=36445&highlight=distribute