Protecting Tables from being viewed

[nxqviet]

Hi all,

I need help to protect my tables from being viewed by my users.
Basically, i want to them to view data via forms, which is much easier
to control. To prevent this problem, I disabled all menu and the
database window on startup, but they can easily bypass the strartup if
they know how.

Also, all my link tables are linked tables, but they still need to
show up on the database window anyway (am I right? Is there anyway to
avoid that?). Also, I tried to create MDE files, which did not help
because they only lock code-based objects.... I ran out of options, if
you have any suggestion or solution, please help. I need this bad...

Thanks,

V_

 

[Rick Brandt]

Hi all,

I need help to protect my tables from being viewed by my users.
Basically, i want to them to view data via forms, which is much easier
to control. To prevent this problem, I disabled all menu and the
database window on startup, but they can easily bypass the strartup if
they know how.

Also, all my link tables are linked tables, but they still need to
show up on the database window anyway (am I right? Is there anyway to
avoid that?). Also, I tried to create MDE files, which did not help
because they only lock code-based objects.... I ran out of options, if
you have any suggestion or solution, please help. I need this bad...

Access has lots of ways to hide stuff from "users who don't know how". To
protect tables from "users who do know how" you pretty much have to
implement user level security (advanced topic and still hackable).

There is a way to disable the shift key. You could do that to the copy you
give users and leave your development copy alone. This again falls into the
category of whether the user knows about it (and how to undo it) or not, but
it does raise the bar quite a bit. See link for details...

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

 

[Jeff Boyce]

?Explain to your users that they are free to mess in the tables, but if they
"break it, they bought it"?<g>

Is there something they feel they can do better via the tables than via the
forms?

Consider marking the tables as Hidden, and making sure your options include
not showing Hidden or System tables.

?!get new users?!

JOPO (just one person's opinion)

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Aaron Kempf]

if you want to protect your tables-- then keep them in SQL Server

Access MDB is literally impossible to secure

 

[nxqviet]

?Explain to your users that they are free to mess in the tables, but if they
"break it, they bought it"?<g>

Is there something they feel they can do better via the tables than via the
forms?

Consider marking the tables as Hidden, and making sure your options include
not showing Hidden or System tables.

?!get new users?!

JOPO (just one person's opinion)

Regards

Jeff Boyce
Microsoft Office/Access MVP








- Show quoted text -

Yeah, because there are many level of users, one group of user
shouldn't able to see stuff of the others'. that's the problem. I'll
try to disable the Shift button.

 

['69 Camaro]

Hi.

To prevent this problem, I disabled all menu and the
database window on startup, but they can easily bypass the strartup if
they know how.

Implementing User-Level Security would solve that. Only members of the
Admins group can change the shift key bypass property. Your regular users
shouldn't be members of the Admins group.

Also, all my link tables are linked tables, but they still need to
show up on the database window anyway (am I right?

Not necessarily. Each form's or report's RecordSource Property can use a
SQL statement that references the back end tables. For an example of how to
do this, please see the tip "How to use a form to update records from a
table in a remote database with a database password, without linking to that
table or writing VBA code for an ADO or a DAO connection, and hide that
password from the user" on the following Web page:

http://www.Access.QBuilt.com/html/forms.html

In this case you don't need the password, so you can safely ignore the
references to the database password in the explanation and the code.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Aaron Kempf]

user level security is a PITA and it doesn't work-- and it requires you to
secure ALL of your databases

what an awful awful reccomendation

 

[Joan Wild]

user level security is a PITA and it doesn't work-- and it requires you to
secure ALL of your databases

No it doesn't.