MS Access 2003 Security Implelementation Problem

[aball65]

I'm running a networked installation of MS Access 2003 and am trying to implement security (i.e., read only users, read-write users, etc.) on my database. After running the User Level Security Wizard, I get the following error when I try to open the database:

"You do not have the necessary permissions to use the 'my.mdb' object. Have your system administrator or the person who created this object establish the appropriate permissions for you."

Any ideas?

Thanks!

 

[boblarson]

I'm running a networked installation of MS Access 2003 and am trying to implement security (i.e., read only users, read-write users, etc.) on my database. After running the User Level Security Wizard, I get the following error when I try to open the database:

"You do not have the necessary permissions to use the 'my.mdb' object. Have your system administrator or the person who created this object establish the appropriate permissions for you."

Any ideas?

Thanks!

yes, you need to open the database by means of a shortcut that SHOULD have been created as you went through the wizard process UNLESS you chose the choice to join the workgroup (not the good option).

you can open using a custom shortcut you create but you need to know where the MDW file that was created for your database is located. I, would actually suggest using Headway Shortcut Builder for creating a shortcut because it takes the guesswork out of where to put the quotes, etc.

 

[aball65]

I don't have admin rights on my PC so I can't install that Headway tool. A shortcut was created and here's what the target looks like:

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\Documents and Settings\BallAW\Desktop\Interagency Program Office\Risk Mgmt Database\DoD VA IPO RMDB r3.mdb" /WRKGRP "C:\Documents and Settings\BallAW\Desktop\IPO\Risk Mgmt Da

It appears to have been truncated and it also looks like it includes the workgroup parameter you mentioned. What do you recommend?

Thanks

 

[boblarson]

Looks like your paths are a bit long for it and it truncated. You could see if you could manually add the missing text, but I'm thinking it probably is at the max. You may want to move the database and shortcut to something like

C:\Database

to shorten things up a bit.

 

[aball65]

That worked. Thanks a ton!

Now I have another question. My database needs to be accessed by other users using a network shared drive. To do this, would I simply need to do the following:

1. Create database user accounts for these people
2. Copy the .mdb and .mdw files from my desktop to a shared drive
3. Have each user create a shortcut on their desktops pointing to the .mdb and .mdw files on the shared drive

Thanks again.

 

[boblarson]

That worked. Thanks a ton!

Now I have another question. My database needs to be accessed by other users using a network shared drive. To do this, would I simply need to do the following:

1. Create database user accounts for these people
2. Copy the .mdb and .mdw files from my desktop to a shared drive
3. Have each user create a shortcut on their desktops pointing to the .mdb and .mdw files on the shared drive

Thanks again.

First of all, the database should be split (frontend / backend). The backend resides on the server along with the mdw file. The frontend should be a copy on each user's machine. You can then have a master frontend on the server which you use to make changes and then using an auto updater, your users can have the latest frontend (see my tool - at site in signature, or Tony Toews' tool).

See here for more on splitting your database.

You should not share a frontend file as it will highly increase the likelihood of corruption. And sharing a single, non-split, database file increases the likelihood of corruption even more.

 

[aball65]

Wow. I didn't know Access supported a client / server architecture. I'll read over the link. Thanks again. You've been EXTREMELY helpful.