Yes, it was the area pointer, thanks for the reply. I had overlooked that the DB containing the date/timewas modified. A third party updated the code and for whatever reason moved the system time to another DB. I wasn't thinking of the area pointer being wrong becauseI was more focused on the Windows dateincrementing. Which was different from theHMI screens, which just kept resetting to thedefault date/time of the empty DB (w/1 sec refresh). Not sure whythe Windows date/time didn't do the same.