CFUPDATE and CFINSERT are the devil's tools. Well not quite; they are designed to keep the learning curve of CF low, but (IMHO) should never be used unless you need that low curve. If you know how to write the SQL statements for INSERT and UPDATE, then using CFUPDATE and CFINSERT is generally a bad idea. Your uncle's nova (CFUPDATE) generally works, but if someone gave you a free <fill in car name> (CFQUERY), with which gas and insurance were cheaper (performance), but you had to go pick it up 10 miles away (initial coding), would you take it?
Bottom line, the app engine shouldn't know anythign about your database, so don't let it. My $0.02, barneyb > -----Original Message----- > From: Hawkes, Keith A CIV [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 18, 2003 11:19 AM > To: CF-Talk > Subject: NOT A CRITICAL ISSUE - <CFUPDATE> vs <CFQUERY> UPDATE tablename > e tc. > > > I was going absolutely bonkers not understanding why <CFUPDATE> wasn't > always updating a field consistently, so I switched to <CFQUERY> and > updating the fields with SQL commands and it's now working perfectly. I > wasn't using any session or client variables other then those passed from > the form, but this one field (critical, of course) wasn't always updating > using <CFUPDATE>. Sometimes it would and sometimes it wouldn't. Hitting > the refresh button a few times would occasionally update the field. Has > anyone else come across something like that? > TIA, > Keith > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq 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 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
