Is this possible? If database already in use, limit all new users to read-only access.

  • Thread starter Thread starter Ben Smith
  • Start date Start date
B

Ben Smith

Is it possible that when a user opens an mdb to determine if other
users are currently using the mdb and if they are only allow the current
user to read-only access?

I'd like to do all of this through VBA code if possible.

Thanks.

Ben
 
Hi Ben,

Partly possible, you can refer to the code in the article to list the
current users logged into the database:

HOW TO: Check Who Logged into Database with Jet UserRoster in Access 2000
http://support.microsoft.com/?id=198755

However, it seems it is not possible to change the current user to
"read-only", any user will have the explicit creating objects permission by
default. For more about the security questions, please read the security
FAQ:

ACC2000: Microsoft Access Security FAQ Available in Download Center
http://support.microsoft.com/?id=207793

Please feel free to reply to the threads if you have any concerns or
questions.


Sincerely,

Alick Ye, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.



--------------------
| From: "Ben Smith" <[email protected]>
| Subject: Is this possible? If database already in use, limit all new
users to read-only access.
| X-Tomcat-NG: microsoft.public.access.security
|
| Is it possible that when a user opens an mdb to determine if other
| users are currently using the mdb and if they are only allow the current
| user to read-only access?
|
| I'd like to do all of this through VBA code if possible.
|
| Thanks.
|
| Ben
|
|
|
|
|
 
I want to add a bit to what TC and Alick have already said. I have the same
question as TC -- why do you want to do this? It is not typical to allow
only one user to modify data in a database. One of the purposes of a
relational database is to allow multiple users to enter and modify data at
the same time. Trying to circumvent that would not only be very difficult,
if not impossible, but not a good use of the database.
 
I suspect he will say (if he answers at all):

"Because when I let several users enter data at the same time, I get runtime
errors, and I want to prevent these." :-)

TC
 
Back
Top