Well, let me see if I can describe the problem properly.
We have 7 computers that are all alike; same hardware, same OS (XP SP2 fully patched), same programs. These computers run just one program that is used to measure veneer. I wrote the program so I know what it is doing. The program runs on all the computers except one. This one computer is a backup computer and it was working a couple of months ago. Today, when we tried to start the program on this computer, we get an error that says, "Invalid argument to date encode."
The section of code this occurs on is a class that looks at the date of some backup files and determines if the files are older than two weeks. If I remove this class, the program works, so we know the problem has to do with file dates.
Here is the kicker. If we take an image from a working computer and put it on this hardware, the program works. If we take an image of this computer and put it on a "working" computer, the program doesn't work. This means it had something to do with Windows and not the hardware.
We've looked at the Region and Language and it is correct. Changing this doesn't fix anything.
We've looked at the registry setting in HKEY_USER\.DEFAULT\Control Panel\International and the short date is correct.
We've looked at the date/time setup and it is correct.
We've deleted the directories and recreated them and the files and still no joy.
What else are we missing in XP that would affect the file date? It's driving us bonkers!!!!
James P. Cottingham
-----------------------------------------
I'm number 1,229!
I'm number 1,229!
We have 7 computers that are all alike; same hardware, same OS (XP SP2 fully patched), same programs. These computers run just one program that is used to measure veneer. I wrote the program so I know what it is doing. The program runs on all the computers except one. This one computer is a backup computer and it was working a couple of months ago. Today, when we tried to start the program on this computer, we get an error that says, "Invalid argument to date encode."
The section of code this occurs on is a class that looks at the date of some backup files and determines if the files are older than two weeks. If I remove this class, the program works, so we know the problem has to do with file dates.
Here is the kicker. If we take an image from a working computer and put it on this hardware, the program works. If we take an image of this computer and put it on a "working" computer, the program doesn't work. This means it had something to do with Windows and not the hardware.
We've looked at the Region and Language and it is correct. Changing this doesn't fix anything.
We've looked at the registry setting in HKEY_USER\.DEFAULT\Control Panel\International and the short date is correct.
We've looked at the date/time setup and it is correct.
We've deleted the directories and recreated them and the files and still no joy.
What else are we missing in XP that would affect the file date? It's driving us bonkers!!!!
James P. Cottingham
-----------------------------------------
I'm number 1,229!
I'm number 1,229!