Keep track of the date twice -- original install, and last time accessed. If the program is started before the last time accessed date, then bomb.

You also might want to track the amount of time the app is active for. That will keep them from setting the date to the same date over and over. When the app has been active for 24 hours or whatever, then bomb.

>I am sending out beta versions of a program and would like to know how to have it stop working on a given date without the user being able to 'get around' this. I have thought of just putting a date check at the beginning of the program, but if the user changes the system date before startup they will be able to use the program. Any suggestions would be greatly appreciated.