Prevent Users From Importing Tables Into Another Database

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

I have a database that uses a form-based authentication
screen, allowing users access to varying detail reports.
I am disabling the SHIFT key so that the autoexec macro
cannot be overridden.

In short, I need to prevent users from importing my tables
into other databases or linking to them. I want to avoid
a database password, as having to share it with each user
would defeat the purpose fo creating one. A split
database is not an option. Any suggestions?
 
You can do this by using Run With Owner Permission (RWOP) queries for
**ALL** access to tables (including SQL statements in code, etc), and then
disallowing direct access to ALL users in the database. This is a complex
area, and one which will require you to do a good bit of experimentation and
reading. I would assume that you haven't implemented the builtin security
for your database; this would be REQUIRED to achieve what you want. Also,
why is splitting the database not an option? There is no real difference
between local tables and linked tables ... if you have multiple users (as is
indicated by your post), then a split database solves a lot of problems.
 
Thanks Scott.

The reason I can't split the database is that it will
unfortunately need to be distributed to several users in
its entirety, as there is no common server to host from.
Given the Access limitations of the end user group, I need
to limit potential areas of confusion (e.g. a split
database).
 
Note that if you do not split the database, any upgrades to your app may
overwrite the user's data. If your database is basically read-only (user
makes no entries, edits, deletions), keeping the database in one file may be
ok. However, if your users will be making changes to the data, splitting is
warranted and will save you a lot of headaches later on.
 
Back
Top