securing access database

[Shift838]

I want to secure an access database. I already have it securing programatically, but I do not want the users to be able to by pass to go to design mode. I want it to come up as a application and not see access at all. How can this be done?

 

[FancyPrairie]

If you secured your database properly, then the user cannot make design changes. With that said, you could save your database as a .mde. Then the users can't see the internals.

 

[eggy168]

I want to know users can still create their own queries under .mde extension?

 

[RobSindle]

Yes, THAT they CAN do. Look at securing with User level security (and a workgroup .mdw file).

 

[Shift838]

can access use NT Authentication to use a users logon credentials?

 

[RobSindle]

THe short answer is NO, NT authentication and Access workgroup security are separate. You CAN however, find out the user's authenticated NT username (i.e., "who they are logged into NT as") and use that info from within your Access App if you want.

 

[psemianonymous]

I recommend using the Windows username to "figure out" who is using the database; if that isn't secure enough, then I recommend Access/JET built-in security--that's as secure as you can get. I discuss all these options (and more) in the FAQ:

Gauging your security needs; alternatives to Access/JET security faq181-3893


Most people don't care about security but just want to know "who" is using the database, e.g. entering records, modifying records. I've done several databases with Access/JET security and I've done a few that simply pick the username from Windows. The ones that pick from Windows are much less overhead in ALL aspects, and are intuitive to boot!