How to compile to prevent user access to table or query ?

P

Peter chin

To the MVPS,

I had compile my access database to mde version but the table and query part
still allow it see design or open. Current work around is to hidden the it
all. But somehow rather for those user had gone for Access training, they
would be able to unhide it and manipulate from it. This is a big risk.

Please help and is there anyway to dim that to prevent user access to it
just like they can't access to Form and report ?

Thanks.

Peter.
 
J

Jeff Conrad

in message
To the MVPS,

I had compile my access database to mde version but the table and query part
still allow it see design or open. Current work around is to hidden the it
all. But somehow rather for those user had gone for Access training, they
would be able to unhide it and manipulate from it. This is a big risk.

Please help and is there anyway to dim that to prevent user access to it
just like they can't access to Form and report ?
Click to expand...

Here is a past post of mine on this issue which may help:

A really good wedgie may do the trick, but failing that......

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, 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

For information on creating custom menu bars and toolbars, please see
the following link for good information:

http://www.ltcomputerdesigns.com/JCReferences.html#MenuBars

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 listed at the following link before
beginning. Also, practice on dummy databases until you are really
comfortable with it.

http://www.ltcomputerdesigns.com/JCReferences.html#Security

Good luck,
 
J

John Vinson

Please help and is there anyway to dim that to prevent user access to it
just like they can't access to Form and report ?
Click to expand...

Implement Access security, and give these users accounts with only
Open/Run (and not View Design or Modify Design) privileges on the
tables and queries. Get a copy of the Microsoft Security Whitepaper
and read it carefully - security is complicated and it's fairly easy
to mess it up!


John W. Vinson[MVP]
 
A

Albert D. Kallal

Peter chin said:
To the MVPS,

I had compile my access database to mde version but the table and query
part
still allow it see design or open. Current work around is to hidden the it
all. But somehow rather for those user had gone for Access training, they
would be able to unhide it and manipulate from it. This is a big risk.

Please help and is there anyway to dim that to prevent user access to it
just like they can't access to Form and report ?
Click to expand...

It depends on how "hard" you want to lock things up. In MOST cases for
MOST users, just disabling the shift by-pass key, and then using the
tools->startup to hide all of ms-access is sufficient.

Try downloading the 3rd example here:

http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

"click here for access 2000 merge example with ms-access interface hidden"

The above takes no code, and no security. If you disable the shift by-pass
key, then users will not see ANY of ms-access.

It is not clear how much you need to lock things up. The above has no
security, and will not prevent users from copying the data, or copying the
queries into another database,but it will certainly keep you users out of
the
"ms-access" part.
 
Top