Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Advice on disabling a database

Status
Not open for further replies.

PaulSc

MIS
Aug 21, 2000
148
GB
hi,
after a bit of advice on something we need to do please.

We have a number of Access databases which we would like to "disable" after a set period of time.

i.e. a new UAT version of a database has 28 days to be signed off by client but if not signed off it becomes unusable - Similar I guess to shareware crippling..

We can do this using the autoexec to bring up a form with a date check and lock down the db (disable f11 etc) and after the expiry date shut down the database but wonder if anyone has any other suggestions as to how to achieve this effect

TIA
PaulSc
 
A sneaky way would be to check for the expiration date, and if met, use VBA to delete critical database objects.

[noevil]

Illegitimi non carborundum.
 
Sup?

I think your safest best bet would be to do a test, and not even let the user in the database unless it is valid.

In order to deploy the front end of a split database, I stored a value in a table on the back end, and then rather than let the users open the database directly, I created a shortcut to a small Java app that read the file and looked if it was newer; if so, copied a new file to the users then opened it. You might try some variation of that.

This would allow you to keep the old stuff that never got certified by the customer.

Just a thought.

"If it's stupid but works, it isn't stupid."
-Murphy's Military Laws
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top