Database Security (Access 2000)

[tricky29]

I have recently written a database that runs from an autoexec macro. I wish to make the database secure so as no one has access to the database code. My plan is for me to keep an original with full access to the software with then a secured version to be distributed to others. At the present I have gone in to Tools>Startup and deselected all the tick box options. This would appear to work as it seems to disable access to the database windows. Can anyone tell me whether or not this is secure or whether there is a way for others to re enable access to the database. If this is the case and it is not secure, what steps can I take to acheive my goals ?

 

[DoogieB]

If I understand you correctly, setting some of the options such as not displaying the database window or the design tools will keep the least knowledgeable user out, but there are simple ways to get right in, like hitting F11 to show the database window. Also, if any code blows up, the user may have the opportunity to go into debug mode. Not something we want at all! Here are two options for you to investigate in the MS Help files:
1) Security Wizard.
I'll admit that I've never had cause to use this one yet, but it basically allows you to do NT-like things with work group permissions.
2) Create an .mde file.
This works best for a split database, but I've used it extensively to "button up" a database I don't want anyone to get into, even by accident. It compiles the source VBA code into p-code thus removing any design functionality. Here's what you CAN'T do with an .mde file:
- Add,modify,remove object lib. references
- Import/export forms,reports,modules
- Change or view source code (there isn't any there!)
- Edit/create reports, forms, or modules

I hope this gives you some options to explore.

 

[Lightning]

Read these FAQs for more info on Access Security:

FAQ181-83

FAQ181-1131

FAQ181-1164

Access security is not difficult to set up IF you take it one step at a time.

Good Luck

Lightning