CFPARAM and CFQUERYPARAM are two entirely seperate tags. If you are seeing (param1) stuff in the SQL statements then it is because SQL 'bind parameters' are being used.
One way to get CF to use bind parameters is to use CFQUERYPARAM. If you are not using CFQUERYPARAM, but you are using CFINSERT or CFUPDATE, that would suggest that these tags are also capable of using bind parameters. If so, and you want to prevent the (param 1)... output, you could re-write the CFINSERT or CFUPDATE tags into a regular CFQUERY with a manual "INSERT INTO [table] ([fields]) VALUES [values]" or "UPDATE [table] SET [field1]=[value1], [field2]=[value2], ... WHERE [condition]" type of statement, as appropriate. Hopefully that helps and hasn't confused things further? On 10/25/06, Indy Jones <[EMAIL PROTECTED]> wrote: > As best I can tell, I'm not using CFParam. I've searched the code and I had > someone else search. My PC's being stupid, so I'm not staking my life on it, > but I'm not seeing it. Why does the server think I am? Why am I getting the > (param1) (param2) crap? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/SQL/message.cfm/messageid:2593 Subscription: http://www.houseoffusion.com/groups/SQL/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.6
