I think a security issue

[Guest]

I was wondering if there is a way to permit only one person to use a database
at a time? With our current database, if I was working in it and my
assistant would open it at her desk also, it would not prompt her to let her
know it was already in use. Is there such a command to do this. It sure
would save us some errors. Our procedure now is to yell across the room, hey
is anyone in the program. That is if we remember to do so.

 

[Douglas J. Steele]

Access is multi-user enabled out of the box.

What you really should do, though, is split the application into a front-end
(containing the queries, forms, reports, macros and modules), linked to a
back-end (containing the tables and relationships). Only the back-end should
be on the server (or on a shared folder if you're not using a server): both
you and your assistant (and whomever else may require access to the data)
should have your own copy of the front-end, preferably on your hard drives.

 

[John W. Vinson]

I was wondering if there is a way to permit only one person to use a database
at a time? With our current database, if I was working in it and my
assistant would open it at her desk also, it would not prompt her to let her
know it was already in use. Is there such a command to do this. It sure
would save us some errors. Our procedure now is to yell across the room, hey
is anyone in the program. That is if we remember to do so.

If you'll both be working on the same database in design mode, open it
exclusively. That's one of the options on the Open menu item.

If you'll just be using the application, sharing the same data but not
updating the structure of forms, tables, etc., and for routine use (as opposed
to developement), follow Douglas' advice and split the database.

John W. Vinson [MVP]