I want to run a program on a CD that links to a password
protected access 2000 database. However, although the
password is embedded, as the system cannot write the
access.lockfile to the cd it will not connect.
Is there any way of protecting the database but still
gaining access

"Steve Bradley" <(E-Mail Removed)> wrote in message news:<091e01c34a09$0bc189a0$(E-Mail Removed)>...

> I want to run a program on a CD that links to a password
> protected access 2000 database. However, although the
> password is embedded, as the system cannot write the
> access.lockfile to the cd it will not connect.
> Is there any way of protecting the database but still
> gaining access

From a previous google poster:

"Ensure your app database is opening read-only and, if linking, ensure
your data database is opened in read-only mode. This ensures Access
does not try to create an .ldb on the CD and your app will play
happily. Forget to do this and Access will try to create an .ldb on
your CD, which brings out the big bad meanies and the app will fail."

Also, you realize that the database password is easily determined
using code that is freely available all over the web? And, since it
must be hardcoded in the linking database - in plaintext form - you
can find it in a few seconds using MS Word (for example)! You should
not assume that you are getting a strong level of security from the db
password. It is, however, fine for disouraging accidental use of the
db by technologically unsophisticated users.

HTH,
TC