vbainchicago
Technical User
I created an Access db for a small printing company. The final "product" I left them with was an mde file.
Everytime I do a database for someone I haven't worked with, I always include a module that will cause the db to "expire" after a certain date. For example:
Function Terminate()
If (Date >= #6/1/04#) Then
DoCmd.RunCommand acCmdExit
End If
End Function
I set every form's (including the form they see when they open the db)on load event to refernce this module.
Wouldn't you know, the company is stiffing me on the bill.
My question is - how can they defeat my expiration policy? I've only found way - roll the date back on the pc. They would have to know it was the date that triggered this event through, and I don't think they can figure this out.
Does anyone have any other ideas or practices they use to ensure that if someone doesn't pay your for your work that the databse will disbale itself?
I've set the terminate module in the past to delete tables instead of just exiting, but that was a little harsh.
Thanks for any feedback!
Everytime I do a database for someone I haven't worked with, I always include a module that will cause the db to "expire" after a certain date. For example:
Function Terminate()
If (Date >= #6/1/04#) Then
DoCmd.RunCommand acCmdExit
End If
End Function
I set every form's (including the form they see when they open the db)on load event to refernce this module.
Wouldn't you know, the company is stiffing me on the bill.
My question is - how can they defeat my expiration policy? I've only found way - roll the date back on the pc. They would have to know it was the date that triggered this event through, and I don't think they can figure this out.
Does anyone have any other ideas or practices they use to ensure that if someone doesn't pay your for your work that the databse will disbale itself?
I've set the terminate module in the past to delete tables instead of just exiting, but that was a little harsh.
Thanks for any feedback!