By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,446 Members | 3,019 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,446 IT Pros & Developers. It's quick & easy.

Hiding a table contents using security

P: n/a
Hi all,
Is it possible to have the table view hidden, but allow a user to view the
table contents through a query or linked form ?

Thanks in advance.

Gerry Abbott

Nov 18 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Gerry,

You can force your table to become hidden from the database window by
prepending its name with "MSys". Access hides all tables that have the
"MSys" prefix, as they are considered system tables and hold some great
stuff, like all the objects in your database.

Nov 18 '05 #2

P: n/a
HI Steve,
Thanks for the quick reply .

But can the user not just select unhide system tables, from the options
menu?

Gerry

"Steve" <th*********@gmail.com> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com...
Gerry,

You can force your table to become hidden from the database window by
prepending its name with "MSys". Access hides all tables that have the
"MSys" prefix, as they are considered system tables and hold some great
stuff, like all the objects in your database.

Nov 18 '05 #3

P: n/a
Definitely. If you want table security, use Access' built-in security
system (it has table-level security, I believe) or write your own.
Incidentally, it would be pretty tough to write custom security that
would prevent users from accessing a system table. What I usually do
with all my programs is set a startup form, hide the database window,
disable design view, etc. Then the user can't get to the point where he
can look at tables or any other objects unless you let him. Note that
users will still be able to get into design view, etc. if you don't
disable using the Shift key while opening the database.

Nov 18 '05 #4

P: n/a
Yeah Steve,
think you've confirmed my suspicions, that I cannot directly prevent a user
from looking at the table, if a form based on the table needs to display the
data.
Your suggestion about the shift key disable, with a hidden database object,
is the way to go, along with access security. ((I have some code for
disabling the shift key, and it works fine) .

Cheers.
Gerry
"Steve" <th*********@gmail.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
Definitely. If you want table security, use Access' built-in security
system (it has table-level security, I believe) or write your own.
Incidentally, it would be pretty tough to write custom security that
would prevent users from accessing a system table. What I usually do
with all my programs is set a startup form, hide the database window,
disable design view, etc. Then the user can't get to the point where he
can look at tables or any other objects unless you let him. Note that
users will still be able to get into design view, etc. if you don't
disable using the Shift key while opening the database.

Nov 19 '05 #5

P: n/a

"Gerry Abbott" <pl****@ask.ie> wrote in message
news:D3****************@news.indigo.ie...
Yeah Steve,
think you've confirmed my suspicions, that I cannot directly prevent a user
from looking at the table, if a form based on the table needs to display the
data.
Your suggestion about the shift key disable, with a hidden database object, is
the way to go, along with access security. ((I have some code for disabling
the shift key, and it works fine) .


You can deny permission to the table and use a RWOP query in the Form's
RecordSource. That should result in a form that will show the records in the
table but no ability to open the table directly.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 19 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.