I have written a routine to create a daily archive database by copying tables and queries into a new db. The routine is run from within the original database. Is there any way I can program the backup routine to automatically get the database password of the current db and copy it to the archive db? I can see how it could be a security hole if you were able to access the pwd ... maybe it's just not possible?
I tried parsing the connection string:
...
Set cnn = CurrentProject.Connection
Debug.Print cnn.ConnectionString
...
Result: Database Password shows in the string as ""
I can make the user ENTER the desired pwd - twice, with cross-checks - but it's annoying for user, doesn't guarantee that it's the RIGHT pwd, and I don't know any way to make the input box show the pwd masked with asterisks. I can prompt user to open the archive db exclusive and set the pwd, but I think that's even more troublesome for user, and also doesn't guarantee the right pwd--or even that user really sets it.
This is a non-split, non-secured Access 2K db.
I tried parsing the connection string:
...
Set cnn = CurrentProject.Connection
Debug.Print cnn.ConnectionString
...
Result: Database Password shows in the string as ""
I can make the user ENTER the desired pwd - twice, with cross-checks - but it's annoying for user, doesn't guarantee that it's the RIGHT pwd, and I don't know any way to make the input box show the pwd masked with asterisks. I can prompt user to open the archive db exclusive and set the pwd, but I think that's even more troublesome for user, and also doesn't guarantee the right pwd--or even that user really sets it.
This is a non-split, non-secured Access 2K db.
