Re: CTime Constructor error or XP problem or just me?
I've never had a problem with the time zone, but I have had problems (even
in latest version) with CTime if the time is very near the beginning (jan 1,
1970 I believe). If the GMT is less than your current one it actually ends
up with a -1 time zone which throws an exception that is difficult to catch.
Because of that I always force any invalid date (like from a file with a bad
date) to be at least 2 days into January 1970 before using it. I don't know
if this is related or not. I had the problem with setting my GMT to
Germany, for example, since it is a negative GMT.
Tom
"Chris Hansen" <Chris Hansen@discussions.microsoft.com> wrote in message
news:129E5599-B83D-4B5C-AD82-21409F3E206A@microsoft.com...
I am working a bug report by one of my users. He reports my time
conversion
fails when the computer is XP and set to one specific time zone. I wrote
the
routine below to try to simulate the problem.
Sure enough, when the computer's time zone is set to Casablanca and the
"Automatically adjust clock for daylight saving changes" is NOT checked.
Then the routines converts imporperly.
However, even though I statically link MFC, when I run the check on Vista
I
DON'T get the error. The XP computers are up-to-date with mandatory
updates.
Does anyone have insight into what might be going on?
TIME_ZONE_INFORMATION TimeZoneInfo;
GetTimeZoneInformation(&TimeZoneInfo);
SYSTEMTIME Utc = {2008, 9, 3, 23, 15, 0, 0, 0}, LocalTime = {0, 0, 0, 0,
0,
0, 0, 0};
SystemTimeToTzSpecificLocalTime(&TimeZoneInfo, &Utc, &LocalTime);
__time64_t Test = CTime(LocalTime).GetTime();
printf("Converted = %I64d %s\n", Test, CTime(Test).FormatGmt("%c"));