Access 2002 Security

[hooi]

I've a question on security as the application that i've deployed doesn't ask for username/password when run.

Here is a summary of what I've done:
1. Split the database
2. created a new workgroup, containing a 'superuser' as well as all the other normal users.
3. changed ownership of all the objects to 'superuser'.
4. Removed the default 'Administrator' user.
5. Packaged my application with XP Developer.
6. Install my application at users with setup.exe.

How can I make the authentication window to be displayed when they run the application?

Thanks for helping...

 

[ghudson]

Is it really secured? Can they still open the db without having to log in with a user name and password?

Are you using a custom shortcut to tell Access which workgroup to open the db with?

Here is a sample Target line for a custom shortcut [all on one line]...

"C:\Program Files\Microsoft Office\Office\msaccess.exe" /runtime /wrkgrp "C:\YourWorkgroupFile.mdw" "C:\YourDatabaseFile.mdb" /user superuser

HTH

 

[hooi]

I'm not really sure that it is secure , but I believe my application is now encrypted after the workgroup creation because whenever I zip it, the file size remains the same.

users are still able to run the application without being prompted to enter username and password

 

[Autoeng]

What did you name the new workgroup. You cannot use system.mdw. My guess is this is what you did. As your users can enter the db without loggin on you did not secure your db, but you gave it a good shot. I urge you to read the Microsoft Security Faq's located here...

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp

Read it all first before you try to implement security. In fact, read it twice. Then follow it step by step.

 

[hooi]

Thank you Auteng and ghudson... Your advice have been very helpful to me.

 

[hooi]

Securing the be

My be database is located in a file server which some colleagues have access to, if anyone of them have a full MS Access software, they can just double-click on the be to open it with full permission. Though the fe application has been protected now, how can I protect the be database? Should I encrypt the be or create another workgroup for the be?

Thanks for helping...

 

[Autoeng]

That's been a topic of discussion here in the past. You could make the BE hidden, make the tables in the BE hidden, make the directory that the BE resides in hidden or apply security to the BE. Up to you.

 

[hooi]

Thank you Autoeng.