If your database was replicated, you might be able to invoke such a
scheme, but it could be more work than it's worth. Replication
automatically tags each replica with a unique GUID for each
machine/location. You might be able to read and compare the
replication GUID. Regardless of whether or not it could be made to
work, the security would be at the *application* level, rather than at
a *database engine* level.
You might be better off to properly implement security, including RWOP
queries, to control what can be done with your data. See the Microsoft
security FAQ for additional information. Link in my signature.
The basic problem is that a file-based system such as is used for
Access fundamentally requires the user to access the file from within
the file system. With such access, the user is free to copy files in
almost any fashion. A server-based solution would provide the kind of
isolation from the files that you are looking for.
I would like to prevent an Access database from being
moved to any other computer. Is it possible using VB to
get a unique identifier (GUID) of the computer system on
which the Access database resides which I then can use to
compare to a hardcoded value? Computer GUID or a Windows
GUID? How would I use code to read the registry value?
I am using Access 2000.
=======================================================
Jack MacDonald
remove UPPERCASE LETTERS from email address
Vancouver, B.C. Canada
Info about MSAccess user-level security
www.geocities.com/jacksonmacd