Hi John, No downside. I use these all the time. Obviously the code in the Error HTML window will only execute if an Error is encountered from the "insert" or some coding issue in the Results HTML window.
I think that's just the way the Builders do it. It's been years since I used the builders, but I think the "error" results that is generated is not a "real" Error handler - it's just a message because a known _function wasn't called. To implement a "real" Error handler, you have to use the Error HTML windows. Hope this helps. Cheers.... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xml-extra.net 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 11:30 AM To: [EMAIL PROTECTED] Subject: Witango-Talk: results/error html question Is there any down side to using the results and error html in an insert action? I notice that the new record builder puts the response in a separate results action, and the error response in an else action. But the only way to do real error handling when a dbms error occurs seems to be in the error html. Am I missing something? I found Scott's post on db error handling very helpful. John ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
