I apologize if this is an access issue. Right now I have no idea what the problem is so I am going to ask here first.
I have a human resources database written originally in Access 2003. The backend was MySQL 3.x. Recently we upgraded our servers so I upgraded MySQL to 5.1 as well. I've also upgraded my users from Access 2003 to Access 2007.
With the old versions (2003 and 3.x) when I updated or inserted data into the database the timestamp field would automatically update with the date and time the record was added or changed. Since the upgrade my timestamp fields are no longer updating they're just showing a null value.
This is playing havok on my database beacuse some of my functions work using the timestamp. For instance when I am checking the latest employee hourly rates, I use the timestamp to find the last rate entered. Just this week my HR user told me that none of the rates being sent to the union for union dues purposes were correct. It seem it's because the timestamps from the data entered before the upgrade still exist, but any new data entered after the upgrade have a NULL (or blank) value for the timestamp. My function for finding rates is still returning the greatest timestamp but that timestamp is from the last records entered before the upgrade.
Was something changed in how timestamps work in MySQL? Could the import of data during the upgrade have caused a problem in the timestamp? Is this a problem with access 2007?
Any help would be appreciated.
Thanks
-Craig
I have a human resources database written originally in Access 2003. The backend was MySQL 3.x. Recently we upgraded our servers so I upgraded MySQL to 5.1 as well. I've also upgraded my users from Access 2003 to Access 2007.
With the old versions (2003 and 3.x) when I updated or inserted data into the database the timestamp field would automatically update with the date and time the record was added or changed. Since the upgrade my timestamp fields are no longer updating they're just showing a null value.
This is playing havok on my database beacuse some of my functions work using the timestamp. For instance when I am checking the latest employee hourly rates, I use the timestamp to find the last rate entered. Just this week my HR user told me that none of the rates being sent to the union for union dues purposes were correct. It seem it's because the timestamps from the data entered before the upgrade still exist, but any new data entered after the upgrade have a NULL (or blank) value for the timestamp. My function for finding rates is still returning the greatest timestamp but that timestamp is from the last records entered before the upgrade.
Was something changed in how timestamps work in MySQL? Could the import of data during the upgrade have caused a problem in the timestamp? Is this a problem with access 2007?
Any help would be appreciated.
Thanks
-Craig