sercurity issue #2

[Tim Schiermeyer]

Hello,
Figured out the work around in VBA to drive a make table and reset the
permissions through code, see earlier post. But I have another problem I
just realized, I have forms that are use to enter data on tables. How do I
lock out a users from viewing the table itself but allow them to view the
data through the form?
Thank you
Tim

 

[May]

i suggest you hide database window, you are the only one
who knows how to open it.

May
MCP in Access and SQL Server

 

[Joan Wild]

Hello,
Figured out the work around in VBA to drive a make table and reset the
permissions through code, see earlier post. But I have another problem I
just realized, I have forms that are use to enter data on tables. How do I
lock out a users from viewing the table itself but allow them to view the
data through the form?

You should remove all permissions from the tables, and use RWOP queries.

In addition you need to:

Create custom menus/toolbars for use throughout your application.
Create a startup form (a main menu form if you have one) that is opened on
startup.
Use the features in Tools, Startup to
set the startup form
set your default menu (the custom one you made)
disable all the checkboxes about allowing built in menus, toolbars,
changes etc.
hide the db window (ensure the custom menu you create does not
include the Windows, Unhide item
Click on the Advanced button and uncheck the allow special keys
(this will disable the F11 key, among others)

If you need to bypass these startup features, you can hold the shift key
down while you open the db. If you feel that your users may use this to
bypass your settings, you can disable the shift key bypass - there's an
example in help for doing this(look for AllowBypassKey) or at
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm