Why this discrepancy in time functions?

[CoastalMaineBird · Accepted solution]

Maybe this is it:

I am on EDT right now.

My client is on CDT.

The TIMESTAMP displays show the time in LOCAL TIME.

Suppose the client actually ran the test from 9:39:20 to 9:59:31 CENTRAL TIME.

The TIMESTAMP is smart (?) enough to know that it's on CENTRAL time.

When HE opens the file, I'll bet HE sees it as 9:39:20 - 9:59:31.

However, when I open the file, the TIMESTAMP display is showing the SAME TIME, but in MY LOCAL time: 10:39:20-10:59:31

That is the exact instant he started the test: 10:39:20 MY TIME.

The  string indicator loses the timezone when it is recorded - it cannot change, so it shows the same thing in any timezone.

That makes sense, I will verify this with him. 

[CoastalMaineBird]

Confirmed.   My client (in Central time) opened the SAME data file and it shows 9:39:20 - 9:59:31.

 I wonder if that will change next week (after we switch to standard time).

[rex1030]

It will. Like you said the timestamp display uses the PC's opinion of what local time is. I am sure his clock is respecting the time change. The best way to eliminate discrepancies across time zones is to customize the timestamp indicated with the format time string vi.

[CoastalMaineBird]

Actually, it did NOT, at least on my machine.  That same file shows the same time in my case: 10:39:20.