Locking down an .mdb file

[databasedave]

I have to send an access application out to some people who need to preview it's functionality. What is the best way for me to send this .mdb file to them so they can use it (tables, forms, queries, macros and functions) but still keep them from opeing up the objects and viewing the code behind them? Is there a way of sending the .mdb file out so that objects cannot be seen in design mode and the objects cannot be viewed other than through the flow of the application? As you might have already guessed, I am new at securing an .mdb file for outside use. Your help would be greatly appreciated.

Thanks!

 

[Smart]

You can stop anybody looking at vb code in your database by applying a password as follows
In your database and access your vb code once you have the code on show
select the tools option and then db1 properties (where db1 is the name of your database.
select the protection tab
Tick the Lock Project for Viewing box
enter your password
roberts your mothers brother

 

[ghudson]

You can compile the db by converting it to a MDE. That will prevent them from opening the forms in the design view and also accessing the code window.

 

[Digby]

But will it stop them looking at tables and querry's in design mode? and what about not opening the db window on startup?

My db window does not open on startup, Im going to disable shift on open etc is there any point converting my mdb to mde?

 

[ghudson]

But will it stop them looking at tables and querry's in design mode? and what about not opening the db window on startup?

My db window does not open on startup, Im going to disable shift on open etc is there any point converting my mdb to mde?

No. I suggest you read up on using Access security with a custom workgroup and user permissions to lock down your db. It is not that hard once you understand how to secure your db. Search around for there are thousands of threads related to Access security in this forum.