> Convert(varchar(8), datefield, 1) > Changes the internal representation of datetime data to: > mm/dd/yy format (8 characters) which can be dangerous > for data that spans centuries. ;)
Like a timeline of human history? :) > You were thinking of the ODBC string representation of > datetime data which is not applicable in this case since > the execution plan is compiled and executed on MS SQL > Server side (and not at the ODBC layer). Ahh... okay, that's good to know, thanks. :) Isaac Dealey Certified Advanced ColdFusion Developer www.turnkey.to 954-776-0046 ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
