Security of database

I have a database that has a front end and back end linked together. I need to install this database for someone else to use, but I don’t want them to be able to see anything behind the scenes (tables, queries, forms, reports, relationships). Nor do I want them to be able to open anything in design mode and change anything. All I want them to be able to do is open the database and run it by using the forms given. Basically I don’t want them to change anything nor be able to see how it was designed to copy it. What is the easiest and simplest way (without locking myself out). I’ve played with this a little but when I’ve tried something, it installed something on my harddrive to lock me out of ALL my databases, not just one (obviously I don’t know what I’m doing). I then found that file and deleted it to get back in. This database will be installed on someone else’s pc. I just want to have security on this one database.

look into creating a switchboard for that user.

In addition to creating a switchboard for your users you will want to play with the startup properites to find which ones are apporiate to your situation. This will limit the users access to the design view, etc. Make sure you leave yourself a backup door into your database (for development changes).

I can attach an example later is you need one.

S-

I do have a current switchboard that anyone can open. I guess I need more detail help!

Other option is to convert the application to mde file which is a compiled database ie. it does not contain VB source code, for example. Designing forms, macros and modules is also NOT available in an mde file EVER. So BEFORE you convert your mdb to mde, make sure you have a backup of the mdb for developing purposes.

Another way is to secure your database. In a secured database, you can explicitly define which form, table etc. can be accessed by each user. U also can sort the users into groups and assign group permissions instead of assigning permissions to each user. User, User Group and permission information is stored in a WORKGROUP file which is, by default, called system.mdw. You can create othe mdw file by using the Workgroup Administrator. In this case, user authentication required to open the database, but you don't need to convert the mdb to mde.
If you want one of your users to be a 'privileged' user, who is permitted to add and delete users, you can also access the workgroup file from the VBA code.
For more, check Help using keywords like 'security', 'workgroup administrator' 'Secure your database' 'User level security wizard', etc.

Or, you can protect your VB code via a password, but this is available only in Access2K or later versions.

I hope this helps you.
BRegs,
TBÁrpi