M
Maury Markowitz
I have a number of users who I would like to access our SQL Server database
using an Access front-end I have built. The best way to do this would be to
put the ADP onto our filserver, and make a shortcut to it for each user. That
way I can easily deploy changes by updating one file.
However when I try this Access complains that someone else has the file
open. Access help says this is because two people cannot edit the project
objects - forms and such - at once.
Since the application is ONLY used to enter/edit data, this is not a problem
for me. In fact, I don't want the users to be able to touch any of those
things anyway. So how do I get Access to open in a "read only" mode and avoid
this problem?
using an Access front-end I have built. The best way to do this would be to
put the ADP onto our filserver, and make a shortcut to it for each user. That
way I can easily deploy changes by updating one file.
However when I try this Access complains that someone else has the file
open. Access help says this is because two people cannot edit the project
objects - forms and such - at once.
Since the application is ONLY used to enter/edit data, this is not a problem
for me. In fact, I don't want the users to be able to touch any of those
things anyway. So how do I get Access to open in a "read only" mode and avoid
this problem?