G
Guest
Hi,
I need some suggestions on how best to detect/defeat a system date
alteration by the user.
The application is a multi-user timesheet in Access 2000
The backend is stored on a server, frontend is local on each user
machine.
Each user is obliged to complete his/her data at least up to the day
before yesterday.
One of the bosses paranoid thoughts is that an individual user may roll
back the system date on his local machine and thus circumvent the
validation procedures in place.
He is correct, it is possible, but that user would have to keep it up
each and every day.
What would be a good and preferably easy way to check for such date
alteration?
checking the last data entered wouldn't work, it's allowed to enter
future timesheets.
I was thinking to retrieve the system date from the NT server as
"incorruptible" timeserver
best regards
glenn
I need some suggestions on how best to detect/defeat a system date
alteration by the user.
The application is a multi-user timesheet in Access 2000
The backend is stored on a server, frontend is local on each user
machine.
Each user is obliged to complete his/her data at least up to the day
before yesterday.
One of the bosses paranoid thoughts is that an individual user may roll
back the system date on his local machine and thus circumvent the
validation procedures in place.
He is correct, it is possible, but that user would have to keep it up
each and every day.
What would be a good and preferably easy way to check for such date
alteration?
checking the last data entered wouldn't work, it's allowed to enter
future timesheets.
I was thinking to retrieve the system date from the NT server as
"incorruptible" timeserver
best regards
glenn