The new version of firefox is storing their expire date in this 10 digit
format:
and according to the information in the browser this should be the date:
Wednesday, December 30, 2037 9:00:00 AM
Does anyone know how they are converting that number to that date. I have
tried IsDate and Format, but get errors for wrong value. So I am assuming
that the ten digit number does not appear to be a date.
Thanks,
Norm
did you try Julian?
just a thought
mark
Try number of seconds since 1/1/1970 (and compensate for offset from UTC)
I get 2145801600 for somebody 7 hours off GMT which seems too close to be a
coincidence
That's a standard JavaScript Date Object: the number of milliseconds in
Universal Coordinated Time between the specified date and midnight January
1, 1970.
"Norm" <Nor...@newsgroups.nospam> wrote in message
news:O$p3eEnKJ...@TK2MSFTNGP05.phx.gbl...
What Bob said...
Public Function NetTimeToVbTime(ByVal NetDate As Long) As Double
Const BaseDate# = 25569 'DateSerial(1970, 1, 1)
Const SecsPerDay# = 86400
NetTimeToVbTime = BaseDate + (CDbl(NetDate) / SecsPerDay)
End Function
Public Function VbTimeToNetTime(ByVal VbDate As Double) As Long
Const BaseDate# = 25569 'DateSerial(1970, 1, 1)
Const SecsPerDay# = 86400
VbTimeToNetTime = (VbDate - BaseDate) * SecsPerDay
End Function
That gives me this:
?vbtimetonettime(cdbl(#12/30/2037 9:00:00 AM#))
2145776400
?cdate(nettimetovbtime(2145801610))
12/30/2037 4:00:10 PM
Account for UTC, and you're probably there.
--
.NET: It's About Trust!
http://vfred.mvps.org
I see I still have a lot to learn, but think I am going to run out years
first. :-)
Thanks again,
Norm
> I see I still have a lot to learn, but think I am going to run out years
> first. :-)
Yes, this date scheme will stop working in 2038. And it's *NIX's default
scheme, if I recall correctly.
"Planned obsolescence?"
Oh, wait, did you mean YOUR years...?