-
Ok, be patient since I’m new to database connectivity via VB6. I have a project that is using an Access database ( I know, but it’s all I’ve got to work with at the moment.) I need to make the database NOT readable if someone were to try and open the database in Access (or any other program other than the one I’m writing to access it.) What is the “best” or preferred method to:
1. Make an Access database unreadable by anyone who would try to open it
2. Allow my ADO connections to still connect with and read/write/change the database.
If you have any suggestions (preferably somewhat detailed) please share them with me, and everyone.
Thanks a million,
~Acoustic
-
Would a password on the database work? Here is what I found in the office assistant... Hope it helps
Protect a database by adding a database password
Close the database. If the database is shared on a network, make sure all other users have closed the database.
Make a backup copy of the database, and store it in a secure place.
On the File menu, click Open.
Click the arrow to the right of the Open button, and then click Open Exclusive.
On the Tools menu, point to Security, and then click Set Database Password.
In the Password box, type your password. Passwords are case-sensitive.
In the Verify box, confirm your password by typing the password again, and then click OK.
The password is now set. The next time you or any other user opens the database, a dialog box will be displayed that requests a password.
Caution
If you lose or forget your password, it can't be recovered, and you won't be able to open your database.
Do not use a database password if you will be replicating a database. Replicated databases can't be synchronized if database passwords are defined.
Notes
A database password is stored with the database and not with the workgroup information file.
You can't set a database password if user-level security has been defined for your database and you don't have Administer permission for the database. Also, a database password is defined in addition to user-level security. If user-level security has been defined, any restrictions based on user-level security permissions remain in effect.
If a table from a password-protected database is linked, the password is cached (saved) in the database it is linked to when the link is established. This may have unforeseen consequences. For more information, click .
