Securing a database best practice

[Nabeel]

what's the best way to secure an Access database and distribute on CDs, I do
not want users to have access to view code or tables

 

[Joseph Meehan]

what's the best way to secure an Access database and distribute on
CDs, I do not want users to have access to view code or tables

Saving your Access database as an MDE file prevents the following actions:

Viewing, modifying, or creating forms, reports, or modules in Design view.
Adding, deleting, or changing references to object libraries or databases.
Changing code - an MDE file contains no source code.
Importing or exporting forms, reports, or modules. However, tables, queries,
data access pages, and macros can be imported from or exported to non-MDE
databases.

 

[Steve Huff]

The easiest way is to make it into an MDE, this will prevent them from
viewing the code, but not the tables. If you must prevent them from viewing
the tables you will need to apply Jet Security - much more tricky.

 

[Nabeel]

that's what I have been doing . . . .

Can windows domain users be used as users of Access . . I don't want users
to log on to database . . the security should be based on the user name the
person used to log on to windows domain. . .

--
Kind regards,
Nabeel

The easiest way is to make it into an MDE, this will prevent them from
viewing the code, but not the tables. If you must prevent them from
viewing the tables you will need to apply Jet Security - much more tricky.

 

[Nikos Yannacopoulos]

Naabel,

Yes, it can, and it's pretty handy as well! I use this practice
extensively. On the "how", have a look at:

http://www.mvps.org/access/api/api0008.htm

HTH,
Nikos