Linked table limited access?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I do not want others to mine data from my linked table in access. I am
creating an application to distribute with user permissions. The data is in
a linked .mdb. I'm not concerned about the forms.. they will be in a MDE.
I would like the users to be able to read, write, update and delete the data
from within my application, but NOT be able to strip it out using excel or
others that might attach to it.
 
titlepusher said:
I do not want others to mine data from my linked table in access. I
am creating an application to distribute with user permissions. The
data is in a linked .mdb. I'm not concerned about the forms.. they
will be in a MDE. I would like the users to be able to read, write,
update and delete the data from within my application, but NOT be
able to strip it out using excel or others that might attach to it.
Click to expand...

You can deny permissions to the tables and use RWOP (run with owner
permissions) queries for all data interaction. The users would need
permissions on these queries.

Now that I think about this, they'd be able to run the queries and copy the
data out. You really can't deny them access to the data when they need to
use the database.

You can do things to hide the db window, etc so they can't get to the
queries, but they'll still be able to open a form and copy the data from
there.
 
Joan, thx for your help.. Because I'm putting this out with the run-time I
may have a work-around. What do you think of this?

1. open the linked mdb. Save database as "Sys_secure.dbf"
2. Relink the tables.
3. In the Run-Time distribution, place my data file.. "Sys_Secure.dbf" in
the root Windows directory, so that if someone wants to search for .mdb files
on their computer they wont find any. Then it's just a matter of securing
the front end.

Will the app run slowly because the linked tables are in .dbf format?
 
titlepusher said:
Joan, thx for your help.. Because I'm putting this out with the
run-time I may have a work-around. What do you think of this?

1. open the linked mdb. Save database as "Sys_secure.dbf"
2. Relink the tables.
3. In the Run-Time distribution, place my data file..
"Sys_Secure.dbf" in the root Windows directory, so that if someone
wants to search for .mdb files on their computer they wont find any.
Click to expand...

As long as you are happy with the possibility of someone discovering it,
give it a try, but don't be upset if someone finds it.
 
Back
Top