Hi James,
A quick thought - a VB trick is to convert to float and store this. VB uses
double precision floating point to represent dates 0 = 12/30/1899 00:00:00
You could use ColdFusion's DateDiff() to count units between a base date and
the date you need to store. If you needed accuracy to a day, you could use
something like:
DatetoStore = CreateDate("1375","8","13");
BaseDate = CreateDate("1900","1","1");
DaysDiff = DateDiff("d",BaseDate,DatetoStore);
and store DaysDiff in the database. Then it's an easy task to rebuild the
date,
RebuiltDate = DateAdd("d",DaysDiff,BaseDate);
Just an idea,
Ben
"James Silva" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
>
> Heres the problem, after some testing, it seems that MSSQL doesnt like
dates
> before 1753. I need to support dates back to 1600.
> Any ideas? (i normally would do a lot more research before posting, but i
need
> to get back to the client asap).
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
