Dates Handled Differently in XP Home?

Dan Shafer revdan at
Thu Sep 23 02:33:03 EDT 2004

Yes, my script uses the convert command, I'm examining dateItems to 
determine whether the code has expired.

I'll search Bugzilla again with this new info.


On Sep 22, 2004, at 6:28 PM, J. Landman Gay wrote:

> On 9/22/04 5:51 PM, Dan Shafer wrote:
>> A followup. We've now had three of my client's customers experience 
>> the same issue, all on XP. The code works fine on all other OSes on 
>> which it's been tested.
> Does your script use the "convert" command? Are these customers 
> international? This sounds a little like Sarah's pet bug regarding 
> inaccurate time conversions in certain time zones.
>> Strange.
>> Dan
>> On Sep 22, 2004, at 2:25 PM, Dan Shafer wrote:
>>> Are there any documented or known differences in the way dates are 
>>> handled on XP or XP Home vs. other Windows platforms and OS X?
>>> My client has a customer who can't get our software to run correctly 
>>> on his XP Home system. The code that fails checks a code we generate 
>>> based on the day the code is supposed to expire to determine if the 
>>> code is still valid. On Win2k Pro, OS X, and OS 9, the code he has 
>>> been given works. On his XP Home system, it fails every time. If we 
>>> give him a code that expires the next day, it works fine.
>>> He swears the date/time is set right on his machine.
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> Dan Shafer, Revolutionary
>>> Author of  "Revolution: Software at the Speed of Thought"
>>> for more info
>>> Available at Runtime Revolution Store 
>>> (
>>> _______________________________________________
>>> use-revolution mailing list
>>> use-revolution at
> -- 
> Jacqueline Landman Gay         |     jacque at
> HyperActive Software           |
> _______________________________________________
> use-revolution mailing list
> use-revolution at

More information about the use-livecode mailing list