OK, Mike --- I see what you're saying now (I didn't get it the first time) ... you're saying that if you check the user.dat file programmatically, you can see who messed with the system clock, right? I can see where that could be useful in a time-clock situation, but not for this stuff with demo periods.


>Hi Bonnie
>
>>All I do is use the FoxPro DATE() command to get the system date.
>
>So do I, but when the user clicks the clock and changes the date or time (to add more hours to his/her paycheck) it is recorded in user.dat