Try parameterizing your form.issuenumber variable:

Update IssueRegister
        SET IssueStatus = '#form.IssueStatus#',
         Response = '#form.Response#',
            ResponseUserId = '#session.activeuser.USER_NAME#',
         DateofResponse = #CreateODBCdate(now())#        
        Where IssueNumber = <cfqueryparam cfsqltype="CF_SQL_INTEGER"
value="#form.issuenumber#">

If that wasn't the issue, you should use it anyway :)

-----Original Message-----
From: Mickael [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 10:54 AM
To: CF-Talk
Subject: SQL Help

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]

Reply via email to