Tom,
If you use the following, which is an extract from a component I wrote
to convert Active Directory account expiry filetime to utc time, you
get quite different results.
AD stores dates as nanoseconds since 1/1/1601, but I'd say that these
dates are probably seconds since 1/1/1970 or
For anyone still interested in this thread, I thought I might show my final
conclusions...
The database is called Bluechip (a product of HCN, the folks who brought you
Medical Director) and anyone working in the health industry may come across
it.
To get a date from a Bluechip date integer
Ok,
It will be a julian date of some format, which is normally a number or
seconds or minutes past a certain point in time, based on the small number,
minutes.
The standard Java Time is seconds or milliseconds past 1 Jan 1970.
I tried this with yours but it didn't work, you need to
Trying to create a date of 0001/01/01 is alot of fun in CF - I cant
seem to create one using createdate(). I imagine Tom you will have to
use something like the code below to generate a reference date to
compare the integers against.
cfset mydate = createdate(1962,2,2)
cfset refdate = dateadd(d,
The funny thing is, Excel recognises these numbers as dates. If I paste one
of the numbers into Excel, then do Format Cell Date and choose the last
option on the list, Excel will happily turn it into a correct date. To my
thinking, it must therefore be a fairly standard way of formatting a date
OK. Feeling a bit silly now.
#dateformat(718167,d.m.yy)# works a treat. It gives 9.4.66 which is the
same result as Excel (and I assume is correct)
My confusion initially was that #dateformat(718167,d.m.)# gives
9.4.3866 which didn't look right at all so I thought is wasn't working. The
key
.
www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Barry Beattie
Sent: Wednesday, 4 April 2007 10:42 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Date format
no waste at all, IMHO.
I stumbled across
On 4/4/07, Tom MacKean [EMAIL PROTECTED] wrote:
My confusion initially was that #dateformat(718167,d.m.)# gives
9.4.3866 which didn't look right at all so I thought is wasn't working. The
Looks like a bug in the dateformat function. Perhaps you could raise
an issue with Adobe about it.
Actually Excel returns the same result when you force it to use a four digit
year.
Tom
On 4/4/07, Chris Velevitch [EMAIL PROTECTED] wrote:
On 4/4/07, Tom MacKean [EMAIL PROTECTED] wrote:
My confusion initially was that #dateformat(718167,d.m.)# gives
9.4.3866 which didn't look right
I can't see a bug at all. The dateformat function simply diplays the
last two digits of the year of the date as it should. It the date is
stored as 9.4.3866 you would expect a display of 9.4.66 wouldn't you?
What I want to know is why #dateformat(1,d.m.)# is 31/12/1899
and not 1/1/900 ??
On
suggest you refer back to Karen's previous entry and then follow up the
joelonsoftware link, about halfway donn the joelonsoftware post. it might
help
On 4/4/07, rod higgins [EMAIL PROTECTED] wrote:
I can't see a bug at all. The dateformat function simply diplays the
last two digits of the
this
or is it just a dodgy version of CF running on my localhost?
-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Barry Beattie
Sent: Wednesday, 4 April 2007 12:17 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Date format
suggest you
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Tom MacKean
Sent: Wednesday, 4 April 2007 11:18 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Date format
Actually Excel returns
13 matches
Mail list logo
