LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Time stamp not recognized by Excel

Which constant are you referring to? The 126298800 value? If so, then yes, you would need to change it since you hard-coded the subtraction of 5 hours, which is your offset from GMT. In Japan your offset would be different.
0 Kudos
Message 11 of 16
(913 Views)
Yes, that is the constant I am talking about. Is there another way to do this so I don't have to change it?
gasseous

One test is worth a thousand expert opinions
0 Kudos
Message 12 of 16
(911 Views)
Hi gasseous,

You could read the time zone from Windows, then use an appropriate offset.

Cheers,
Brian A.
National Instruments
Applications Engineer
0 Kudos
Message 13 of 16
(884 Views)
LabVIEW can directly return the offset from UTC with the specifier <%z>

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 14 of 16
(872 Views)

Ton,

Thank you for this information. I shall try it and see how it goes. I assume that this means I can do away with the adding and dividing of constants?

 

gasseous

One test is worth a thousand expert opinions
0 Kudos
Message 15 of 16
(865 Views)
The "adding and dividing" of constants has nothing to do with the offset from UTC. As I explained here, it has to do with the fact that LabVIEW measures time from a different starting point that OLE dates. Also, OLE date are in terms of days, but LabVIEW is in terms of seconds. The offset from UTC simply changes the value of the constant, not its need to be there.
0 Kudos
Message 16 of 16
(849 Views)