Thanks for your help. I was using eq instead of = to set session.reportdate. CF did not like.
Mark -----Original Message----- From: Barney Boisvert [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 14, 2005 7:53 PM To: CF-Talk Subject: Re: date error Are you passing in a string or a date object? If the former, use parseDateTime() first to parse the string into a date object. cheers, barneyb On 9/14/05, Mark Fuqua <[EMAIL PROTECTED]> wrote: > The query is actually not throwing an error any more. Fixed the > session.jobId, changed to #session.jobId#, duh. > > But, the query doen't return any records because the date is set to > 1899-12-31. Something to do with the createodbc fuction (or more > truthfully, how I am using it). The date is going in as 1899-12-31, even > though I am passing in (or mean to anyway) 09/14/05. > > Thanks > > Mark > > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:218354 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
