>George,
>
>I downloaded your WindowsTime programs from UT (found out about it via UT). I've been playing around with it and I keep running into a snag.
>
>From the command window I do the following:
>
>

>? utc_time(DATETIME())
>

>
>This works great and returns what I'm guessing is UTC date/time. However, if I go into my Windows Date/Time setup and change my Time Zone to Guam,Port Morsby, the same command line call blows up.
>
>The line of code in utc_time that it seems to be hanging on is:
>
>

>ltresult = ltresult + (loConvert.Get_Bias(ltresult) * 60)
>

>
>Maybe I'm doing something wrong? Any ideas?
>
>Thanks for your help!
>
Rodd,

Since I've never tried to do what you're doing, I can only guess. The data is being retrieved is stored in the Registry. I would be surprised if one of the following two things, done after you changed the time zone information, generated the same result. One, exiting and restarting VFP. Or, two, re-booting the machine.

The routines mostly wrap API calls, so I'd think that the problem that's occurring is on that level rather than with VFP itself.

BTW, what's the error message (if any)?