Bug? DateTime error

Sub Activity_Create(FirstTime As Boolean)
Dim tim,utc As Long
Dim tz As Double
tim = DateTime.Now 'Get current local time
tz = DateTime.TimeZoneOffset 'Get hours offset from Greenwich
DateTime.SetTimeZone(0) 'Set clock to Greenwich time
utc = DateTime.Now 'Grab the time in Greenwich
'DateTime.SetTimeZone(tz) 'Set the clock back to local time
Msgbox(DateTime.Time(tim) & CRLF & DateTime.Time(utc),"")
End Sub

I believe this code should store current time in variable tim, and Greenwich time in utc. However, both times display as UTC time. Also, if you uncomment the line that sets the time zone back, both variables display as local time. My goal is to get local time in ticks into one long variable, and UTC time into another long variable, so I can work with both in some astronomical calculations. No matter what I try, I'm unable to figure a workaround at this point.

Suggestion... It would be ideal if there was simply DateTime.UTC as a function that would return UTC time without having to mess with the timezone offset, or to have to adjust the local time clock.

Please use [code]code here...[/code] tags when posting code.

There is no bug here.

Ticks represent the number of milliseconds passed since 1/1/1970 00:00 UTC. The device (or set) timezone is not relevant.

For further discussion please start a new thread in the questions forum.

Okay, thanks Erel. I believe this is the right way to accomplish what I wanted...

I still think there must be some bug about how two variables are set to two different values yet end up the same, but I'll stay away from that approach with DateTime.

One failed attempt at a workaround was to store the tim and utc values into other variables, even doing a speck of math on them. My theory was that the tim and utc variables were getting set as references to the time in DateTime, instead of to the actual ticks values. So here's the code I tried. It has the same bizarre result, where output times are the same, either both local time or both Greenwich time...

Your code is wrong. As I wrote you should start a new thread in the questions forum.