Protecting DB

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello.
I'm trying to protect an Access Db 2003.
I've already hide the db objects, but it is still possible to link or import
the objects to another Db.
Is it possible to prevent one user to import or link the db objects to
another db?

Thanks.
 
in message:
Hello.
I'm trying to protect an Access Db 2003.
I've already hide the db objects, but it is still possible to link or import
the objects to another Db.
Is it possible to prevent one user to import or link the db objects to
another db?

Hi Luis,

The only way to do this is to implement full blown Access User Level
Security (ULS). You would then deny all permissions on the tables
themselves and create RWOP queries for the users to access the table
information. Assigning appropriate permissions to various database objects
would also be needed.

You could also distribute MDE files (a good idea anyway) which would prevent
tampering with your code and prevent importing of forms, macros,
reports, and modules.

In addition you should create custom menu bars and toolbars to limit
what the users can do. Check under Tools | Startup and set limited
startup properties for your users. Hide the Database Window, select
a startup form, uncheck Allow Special Keys, etc. You may also want
to disable the Shift key bypass for those users who are wedgie resilient.
Details on that technique can be found here:

http://www.mvps.org/access/modules/mdl0011.htm

http://www.mvps.org/access/general/gen0040.htm

If you have never used ULS before, be prepared for a lot of work ahead
of you. ULS is not a trivial undertaking at all so I would recommend
ALL of the following reading material before beginning. Also, practice
on dummy databases until you are really comfortable with it.

Access User-Level Security Links:
http://www.ltcomputerdesigns.com/JCReferences.html#Security

Good luck,
 
Back
Top