AHA!!!  I have discovered how the 30 Dec 1999 came into play, and why my 
default date value was not 1900-01-01.  It's because the CF dateformat function 
inserts the 1999 date...And I was blaming SQL for this.

Just in case you are interested in more detail, I found the following on Ben 
Nadel's site:
http://www.bennadel.com/blog/285-Caution-ColdFusion-Zero-Date-vs-SQL-Zero-Date.htm

When I got rid of the dateformat part in my INSERT, SQL took over, and inserted 
something I can manipulate.

Very interesting...

BTW, thanks so much to everyone for your help and suggestions.  Much 
appreciated!
Martin (a/k/a Donna)
________________________________________
From: Andrew Scott [[email protected]]
Sent: Saturday, September 24, 2011 12:42 PM
To: cf-newbie
Subject: Re: Handling default date in CF-->SQL

rotflmao

Anyway, your problem is going to depend on you. Personally I know that my
SQL 20008 SR2 stores the date as 1900-01-01, so I have a service (a usable
query) that pulls the data in, checks the year is 1900 if it is then returns
null as part of the query.


--
Regards,
Andrew Scott
WebSite: http://www.andyscott.id.au/
Google+: http://plus.google.com/108193156965451149543



On Sun, Sep 25, 2011 at 1:21 AM, Martin, Donna M <[email protected]> wrote:

>
> Oh, my bad...So VERY sorry.  One of my best friends is named 'Scott' (first
> name, that is), and I think it was just habit.  He's a nice guy, by the way.
>
> Again, my apologies...
> Donna (or you can call me Martin (my last name), just to make it even)
> ________________________________________
> From: Andrew Scott [[email protected]]
> Sent: Saturday, September 24, 2011 11:03 AM
> To: cf-newbie
> Subject: Re: Handling default date in CF-->SQL
>
> Seriously,
>
> How do people get my name wrong.....
>
>
> --
> Regards,
> Andrew Scott
> WebSite: http://www.andyscott.id.au/
> Google+: http://plus.google.com/108193156965451149543
>
>
>
> On Sun, Sep 25, 2011 at 12:40 AM, Martin, Donna M <[email protected]>
> wrote:
>
> >
> > Hi Scott,
> >
> > I did not intervene--honest.  But it is defaulting to 12/30/1999.  I
> > suppose I can change this with a cfset.  I imagine I can change this in
> the
> > SQL server settings, but have never looked to see if this is possible.
> >
> > I know NULL's are frowned upon.  Would it be best practice to change the
> > date to the 1900 date, and just not display if <some date?
> >
> > D
> >
> >
>
>
>
>
>



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-newbie/message.cfm/messageid:5622
Subscription: http://www.houseoffusion.com/groups/cf-newbie/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-newbie/unsubscribe.cfm

Reply via email to