Last steps to secure my database

  • Thread starter Thread starter Beth
  • Start date Start date
B

Beth

I have an Access 2000 database with a large number of forms and reports and
it is linked to a backend data file. Against my better judgement I am
having to deploy this database to a user that is intent on damaging the
files so they do not work and then trying to "reverse engineer" the program
to duplicate it. I need this program as locked down as possible. I have
done the following:
User level security with a new security workgroup where admin has no
privileges
converted almost all the queries to select statements in the forms and
reports or in the modules
disabled the database window and disabled the shift key
all code in modules
converted file to .mde

However, the individual will be given a mid level security access code (I
can't stop that).
So far I have found that she can still create a new database and import my
tables and the few queries that I have been unable to convert.
I am concerned I am missing other vulnerabilities.

Is there anything else I can do to secure the database? I am forever
grateful for any help I can get on this.
Thanks,
Beth
 
Converting to MDE is the current main method for protecting your code.

Personally, I have always believed that I own the software, but the
end-users own the data. So I never lock down the back-end data
database; I say that is inappropriate. If they want to mess with the
table structures, they can do so, but then "all bets are off" as far as
support is concerned.

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
Back
Top