I currently have a split database with time sensitive data. The data is locked after 2 weeks, leaving the users a 2 week window to enter/update date. The problem was pointed out that if a user changes there system clock on their PC to an older date, MS Access is using this to set the current date on the frontend. This is leaving the database open to change outside that 2 week window.
Any ideas how I can capture the actual date or the server date from the backend?
This is just an opinion. We as developers have been given a monumental task to protect not only company data, but the integrety of our applications. We go to great lengths to protect the users from themselves. In a situation where you load an application onto a user workstation, you expect them to treat it as they would any company property. The truth is, this same person that is trusted to enter, update and maintain company data should also be expected NOT to change a date time clock on their PC. Many companies remove the ability to change the clock at the OS level thus removing the problem. Getting the time from a server can also be set up from within the OS, if it has to be done.
Because Access has inherant functions to work with dates and times, we have to rely on the program to know where to get this from.
Bottom line is, you shouldn't make this a database problem. Talk to your Desktop support and make it their issue.
J
1
