1.) <@NUMAFFECTED> would not work if Tango did not auto-commit with each action. <@NUMAFFECTED> allows you to see if an insert/update worked, and on how many records.
1.) Others have already mentioned the Transaction Actions that allow you to "group" serveral DB actions into one "block" 2.) (Almost) Every action has the errors HTML where you can handle errors. (Only return, else, Group, and Break actions don't have Error HTML). But it's best to avoid errors as much as possible in the first place. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Wilcox, Jamileh Sent: Wednesday, November 20, 2002 11:34 AM To: Multiple recipients of list witango-talk Subject: Witango-Talk: Tango & MSSQL questions Hi guys. We're running Tango 2000 and MSSQL 2000 on Windows 2000 Server. 1. Is there any check in Tango that confirms that a SQL insert/update action has completed before the web app continues? I need to set up some tafs that will be doing multiple inserts each into multiple tables with several indexes and I'd like to be sure that all actions are completing correctly.* 2. Is there a way to capture SQL errors in Tango (I'd like to present more user-friendly error messages than SQL hands back)? As always, many thanks for your time, attention and patience! *(I remember doing one app some time back where I had problems because I did an insert into one table, then searched for the generated ID to make an insert to the next table; the search would fail because Tango had started the search before the database had finished the update. But I can't find the app and don't remember what setup we were using then.) jamileh wilcox Information Systems OU Physicians (405)271-4647 x54124 [EMAIL PROTECTED] ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
<<attachment: winmail.dat>>
