Prevent User From Accessing Table

[Joe Williams]

I have a small table that has some basic information about the application
stored in it. Without having to go to Access Level user security, is there
any way to restrict the user from accessing this table?

I have read about renaming the table as a system table, but that just hides
the table if I am not mistaken. Is there any other way to make it such that
only an authorized person (namely me) can make changes to the table without
having to go to the extent of the MDW file?

Or, alternatively, is it possible to store information dynamically somehow
in a code module?

Thanks

Joe

 

[Steve Schapel]

Joe,

As far as I am aware, "normal practice" with Access applications is to
prevent users from accessing any tables at all. Provide interaction
with the data exclusively through forms. So, in this case, if you don't
have a form bound to the table in question, the user wouldn't normally
even know it is there. Of course, if they were determined and
sufficiently savvy, they could connect to the table in other ways, so
you would have to decide whether this is a risk or not.

 

[John Vinson]

I have a small table that has some basic information about the application
stored in it. Without having to go to Access Level user security, is there
any way to restrict the user from accessing this table?

I have read about renaming the table as a system table, but that just hides
the table if I am not mistaken. Is there any other way to make it such that
only an authorized person (namely me) can make changes to the table without
having to go to the extent of the MDW file?

Or, alternatively, is it possible to store information dynamically somehow
in a code module?

Thanks

Joe

Without implementing security, there's really no good way to stop a
reasonably savvy user. Even with security, a determined and skillful
user can get at the data - Access security is pretty good but it can
be cracked.

Steve's suggestions, of providing the user with only form view, is a
good start - but that implies that security has been implemented,
otherwise the user can just hit F11 or hold down the Shift key while
opening to bypass your startup form. (Well, yes, you can block this
with some effort).

One possible solution - if you're really averse to security - is to
put this information in an array constant in VBA, and compile the
database into a .mde file for the user. Since the source code is
stripped out of the .mde, the user would not have any way to get to
that data other than what your code provides.

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps