Unanswered: Seeking tricky solution
I have an Access database which I'm selling to a client. The client I'm working with is fairly knowledgeable with Access and will be making edits (designing queries/reports/field additions, etc.) so their also getting the mdb file. What I'm trying to figure out is a way to make it so that I can force (the mdb file) to enter a password after a certain date without a knowledeable person simply remarking out code to bypass the checking routine in the mdb and making a new mde file (the backend is SQL Server and the user will be running the program for several months before the password is asked).
I currently have a function setup which runs on the opening of the main form which matches 2 password type fields in a registration table once a certain date has passed. I've already entered the password in the 2nd field. Once they enter the correct password in the first field, the routine will pass the next time they open the program. If they don't match, it asks the user again to enter the password which is then stored in field 1 of the registration table if it matches. Then the next time the mdb is run, it sees the 2 fields match and doesn't ask again for a password (asking for a password everytime is out of the question). This may not be the best solution so I'm open for any suggestions but it needs to be set up to run on a specific date and then until the correct password is entered (otherwise it exits the application) and not available to another mid-level programmer.
My problem is that it's too easy to simply remove the code in the mdb which calls this (or any type of) registration function (I'd prefer not to do any registry entries.) Since this person is fairly knowledgeable, that could easily be done. I would like to send them just the mde file but that is not possible. So how can I somehow design a piece of hidden code available to only me (that another fairly knowledeable user would be using) in an mdb file which would execute on a certain date?
Last edited by pkstormy; 09-23-05 at 21:28.
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)