Help with Database Security

[GeekyGirl]

Hello,

I have a very basic Access Database that is a contact resource for vendors. I have a Switchboard manager form when you open the database with the option to take you to a Form for the supplier contact information or to 2 different reports.

I have set up security so that I have full access and then a Data Entry user is allowed to edit, add and delete data but no make changes to design of the database. I also have just the minimum toolbars showing.

I set up the security and work group file with no problems. It works great on my computer but when I try to transport it to another computer, I get an error stating:
"You do not have the necessary permissions to use H:/File Name.mdb. Have the system administrator or whoever created this object establish the appropriate permissions for you."

How do I set up the database security and still have the database be portable and be able to be used on any computer?

Also, is there a way to restrict the toolbars for the common users and have the full toolbars for the administrator?

Thanks for your help.

Lisa M

 

[Ron_dK]

Maybe this thread may help

http://www.access-programmers.co.uk/forums/showthread.php?t=64532&highlight=security


.

 

[GeekyGirl]

Thank you for sending the thread. Unfortunately it won't solve my problem. I need to have more security so that the files can't be imported into another database and changes can't be made other than working with the data through the Form I have created.

I was going to post my database but all versions that I have require a log-in (even the one I back-up during the Security Wizard so I'm not sure why that happened.)

Lisa

 

[Ron_dK]

You might try a search on password or protection on this forum.

 

[ghudson]

You have to also provide the user your custom workgroup file. The .mdb and .mdw file should be installed on the users computer. If more than one person will be using the db then you should split the db, but the back end with all the shared tables on the network and link the front end to the back end. The users must have a custom shortcut that points to where the msaccess.exe file is located, where the workgroup file is located and where the actual db is located.

Search the forum for the keywords "system.mdw security shortcut" and my user name "ghudson" for a few good threads on the subject.

 

[GeekyGirl]

I did include the workgroup file in my first attempt to transfer the file. But I did discover that I am not using a shortcut to point to the correct mdw file.

I understand what I need to do now but still have a question. I know this has to do with programming and writing code which is were I am at a lost.

If I have customers purchasing this database and they are downloading a zipped file from a link in an email, how can I make the shortcut if I don't know where they are going to store the database and the .mdw file?

I also read that it is recommended that I create a .MDE file. I have been reading up on it but just need to make sure I have this correct. In making an MDE file, the user can still add data through a form. They just can't acess the code and design components. I'm I on target with this?

Lisa

 

[ghudson]

If you are selling it then I would skip the workgroup security and sell the mde version. That will protect the design of the db and also protect your code. The user can alter the queries and macros in a mde but everything will work as long as the user has Access installed on their computer. If you are selling an Access 2003 db then the user will have to have Access 2003 installed on their computer.

The developers edition [more money out of your pocket to buy it] allows you to create an installation package to install the runtime version of Access. That allows a user without your version of access to use your mdb or mde. There are tons of posts related to this subject if that interests you.

 

[GeekyGirl]

Thanks for all your help.

On microsoft's site, I found part of a chapter on security that discussed securing the database without a password and converting to the mde version that I think I will try.

Maybe down the road I can afford the developer version.