----- Original Message -----
From: Dwayne Cole
To: CF-Talk
Sent: Tuesday, December 16, 2003 1:18 PM
Subject: RE: SQL Problem
Try putting "#" signs around the date field. I had this problem before after my service provider switch from ODBC to OLDBC.
Dwayne Cole, MS in MIS, MBA
Florida A&M University
Certified Advanced ColdFusion Developer
850-591-0212
"It can truly be said that nothing happens until there is vision. But it is equally true that a vision with no underlying sense of purpose, no calling, is just a good idea - all "sound and fury, signifying nothing." The Fifth Discipline - Peter Senge
---------- Original Message ----------------------------------
From: "Tangorre, Michael" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Tue, 16 Dec 2003 12:55:30 -0500
>Try Trimming your vars.... especially since they were text before you
>converted them. If it was char type text there might be some padding that
>you don't see..
>
>
>
>-----Original Message-----
>From: Mickael [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, December 16, 2003 12:56 PM
>To: CF-Talk
>Subject: Re: SQL Problem
>
>
>Hi Michael,
>
>Sorry for the double post but I thought there was something up with the
>list, I posted the first one two hours ago didn't see it on the list and
>sure enough as soon as I post again the both show up
> ----- Original Message -----
> From: Tangorre, Michael
> To: CF-Talk
> Sent: Tuesday, December 16, 2003 12:48 PM
> Subject: RE: SQL Problem
>
> No need to post your question twice.. be patient, someone will respond if
> they know the answer. :-)
>
> -----Original Message-----
> From: Mickael [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 16, 2003 12:42 PM
> To: CF-Talk
> Subject: SQL Problem
>
> Hello All,
>
> I am having problems with an update statement that used to work fine in
> Access with CFMX. I have an issue tracking app that used to have the
>issue
> numbers stored as TEXT, I converted the column to Number a little while
>ago
> and it worked fine. Recently users have been having problems updating the
> records.
>
> My update statement is pretty simple
>
> Update IssueRegister
> SET IssueStatus = '#form.IssueStatus#',
> Response = '#form.Response#',
> ResponseUserId = '#session.activeuser.USER_NAME#',
> DateofResponse = #CreateODBCdate(now())#
> Where IssueNumber = #form.issuenumber#
>
> The error that I get from CF is
>
> The search key was not found in any record.
>
> But if I look in the error window it show my statment as follows
>
> Update IssueRegister_qr SET IssueStatus = 'Closed', Response =
>'completed',
> ResponseUserId = 'Mickael Elmalem1', DateofResponse = {d '2003-12-16'}
>Where
> IssueNumber = 1110
>
> This look correct to me. So I tried running it in access's query window
>and
> I get the same error, yet when I try to search the column for issuenumber
> 1110 Access finds it through its own search utility.
>
> This has me stumped. Any ideas anyone.
>
> Thanks
>
> Mike
> _____
> _____
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
