[AccessD] Database Security

Gregg,
This is what I did.  It's working.
I have a database that shouldn't be moved from the directory where it
resides.
I renamed the primary table.
I created a link to the primary table to itself.
I renamed the link to the original table name.
The database works... All the fields, queries, etc.
If the database is moved to any other location an error message pops up and
closes the database but leaves the Access window open.

Any feedback on this method would be appreciated.

Jim

-----Original Message-----
From: Gregg [mailto:greggs at msn.com]
Sent: Saturday, January 17, 2004 11:13 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Database Security



Is there some magical way to keep an employee from burning a copy of the
database to a CD?  The customer does not want to restrict use of CD burning
so...

if not....

is there a way to encrypt the database with a password?  I see the user
level security will encrypt it for those users but I would rather not have
the hassles of turning that on.  If I could encrypt with a password that I
could pass through in code, I wouldn't worry if anyone took it.

if not....

is SQL a better answer?

Gregg Steinbrenner


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com