Securing tables in MDE

[Kevin]

Hi all,

I'm creating a database to put out on the production
floor. I will be creating an MDE to protect my code but,
as you know, that will not prevent users from importing
the tables into another database. I want to lock this
down completely so the ONLY way to get to the data is
through the forms in the MDE.

An even better solution would be to password protect this
ability so that only I can get to the data, but I'll
settle for the former if that's all I can do.

BTW- I've tried user level security but the results are
either a.) it completely locks me out of the data, or b.)
it doesn't seem to do anything. More than likely user
error, but I can't seem to get around it!

Thanks in advance!
Kevin

 

[TC]

Hi Kevin

Two things.

First, you can do what you want using so-called "Run With Owner Permission"
(RWOP) queries. But - like most of Access security - it is not a job for the
faint-hearted! Google the Access newsgroups for "RWOP queries", & you are
sure to find more information.

Second, it sounds like you have not split your database into a so-called
"front-end/back-end" structure. This means having >two< databases. The BE db
contains all of the tables, but nothing else. The FE contains all of the
queries, forms, reports, macros & mopdules, and links to the actual tables
in the BE. There is a single BE, shared by all users. But each user must
have their own (seperate) copy of the FE, whether it resides on their own
PC, or in a seperate directory (for that user) on the server PC.

Atoring everything in a single database, is (a) a recipe for database
corruption, and (b) makes it difficult for you to roll-out updated versions
of your forms & reports, without destroying the user's data! (With a FE/BE
structure, you just give them a new copy of the whole FE. With an "all in
one" structure, how do you give them a new form, for example, while
retaining the data that they have already keyed-in?)

HTH,
TC

 

[Guest]

Even after splitting, how do you protect the BE?

-----Original Message-----
Hi Kevin

Two things.

First, you can do what you want using so-called "Run With Owner Permission"
(RWOP) queries. But - like most of Access security - it is not a job for the
faint-hearted! Google the Access newsgroups for "RWOP queries", & you are
sure to find more information.

Second, it sounds like you have not split your database into a so-called
"front-end/back-end" structure. This means having >two< databases. The BE db
contains all of the tables, but nothing else. The FE contains all of the
queries, forms, reports, macros & mopdules, and links to the actual tables
in the BE. There is a single BE, shared by all users. But each user must
have their own (seperate) copy of the FE, whether it resides on their own
PC, or in a seperate directory (for that user) on the server PC.

Atoring everything in a single database, is (a) a recipe for database
corruption, and (b) makes it difficult for you to roll- out updated versions
of your forms & reports, without destroying the user's data! (With a FE/BE
structure, you just give them a new copy of the whole FE. With an "all in
one" structure, how do you give them a new form, for example, while
retaining the data that they have already keyed-in?)

HTH,
TC





.

 

[TC]

Secure both db's using the same workgroup file. Ensure that only a special
user 'X' has any access to the tables. Do not give anyone the password to
'X'. Do not give any other users, any direct access to the tables. Then
create RWOP queries, owned by 'X', in the FE. Give all other users, general
access to those queries. By this means, no "normal" user has direct access
to the tables (so they can not access them directly in or from the BE), but,
they >can< access the tables >via the RWOP queries<.

HTH,
TC