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 ________________________________________ From: Andrew Scott [[email protected]] Sent: Saturday, September 24, 2011 10:10 AM To: cf-newbie Subject: Re: Handling default date in CF-->SQL Greg, Sometimes you don't get a choice, I just checked what CFORM defaults to without any intervention and SQL Server is defaulting it to 01/01/1900. -- Regards, Andrew Scott WebSite: http://www.andyscott.id.au/ Google+: http://plus.google.com/108193156965451149543 On Sun, Sep 25, 2011 at 12:06 AM, Greg Morphis <[email protected]> wrote: > > I would just allow NULLs.. dealing with dummy dates is reallya bad deal.. > I'm working with a website 14 years old and the dummy dates are 1/1/1900 > and > sometimes 1/1/2000.. since the website expands the 2000 date range there's > trouble.. so just allow NULLs > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:5617 Subscription: http://www.houseoffusion.com/groups/cf-newbie/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-newbie/unsubscribe.cfm
