Multiple users and design control

[irethedo]

I am using Access 2003 and we have 4 or 5 users of the database at any given time which is working just fine but I was wondering, is there any way to take control and make design changes to forms or reports while other users have them open or is it necessary to find all terminal that have a copy open and log them off before changes can be made?

Is there a way to find out what locations have the database open remotely and lock them out temporarily for routine maintenenace?

I notice the *ldb file when soneone else is logged on

Just wondering

Thanks

 

[M8KWR]

the *ldb file contains the names of the computer which are logged onto the database, you can use notepad to opne this file and it will display them

I do not know a way of modifying the form when uses are in it. I use a seperate database for the back and frontend, so i can make changes to the form, and then kick everyone out for about 30 seconds while the new file is been copied.

The report though, i believe are slightly different. If you modify one then you could just copy and paste it into the file that is been used, as long as no users is still using the old one - but its always best for no users to be in the file. That why I always/only update my copy and then update the central one.

The best way to make sure no users will attempt to log back in, is to delete/rename the copy that the user is using, so if you use shortcuts it would not work. Yo may get phones call to ask why it is not working etc, but i'm sure you could live with that.

Hope this helps.

 

[easyit]

1) split the db in front end (no tables) end back end (only tables).
2) Make the backend network accesible
3) distribute the (compiled/mde) frontend to the users.

Each time you change forms etc, you change them first in your own develop frontend (test etc). Then if ready, you distribute them to your users.

The distribution can be automated. I use a batch file (*.bat) which checks to see if there is a new frontend available, if so it copies it to the local c drive. If not it just starts the present front end. You could develop a system that checks for new frontends when users are in the DB, but I think that that is only needed if the users are never leaving the (frontend) DB. Otherwise, at each startup they will have the latest edition of the front end. NB my users have a shortcut to the batchfile, which itself is located on the server.

Only if you need to make modifications to the backend you would need exclusive access to the backend. With 5 users I would suggest to either phone/email them, or if you use the batchfilesystem, just change it so that the db doesn't start while making changes to the backened. This is a reason why I distibute a shortcut instead of the actual batchfile.

EasyIT