dbaccess commit transaction

Hi All. I have a file with sql statements and run it by dbaccess from command line. My file contain a lot of sql statements inside transaction. But trnsaction has been commited when any statement has syntax error . I need rollback transaction when any statement has any error during dbaccess session works. Please give me advice to resolve given problem. I can't understand behavior of dbaccess in the given case. Can anybody explain me that? Best regards, Konstantin.

dbaccess carries on after an error when running a script from the command line by default. There's an environment variable you can set, DBACCNOIGN=1, I think, that causes it to stop processing after an error has occurred. Therefore, if you've issued an BEGIN WORK statement, it should rollback when it crashes out. > -----Original Message----- > From: forum.subscriber@iiug.org > [mailto:forum.subscriber@iiug.org] On Behalf Of Konstantin .... > Sent: 05 November 2003 17:58 > To: ids@iiug.org > Subject: dbaccess commit transaction [2137] > > > Hi All. > > I have a file with sql statements and run it by dbaccess from > command line. > My file contain a lot of sql statements inside transaction. > But trnsaction has been commited when any statement has > syntax error . I need rollback transaction when any > statement has any error during dbaccess session works. > > Please give me advice to resolve given problem. > I can't understand behavior of dbaccess in the given case. > Can anybody explain me that? > > Best regards, > Konstantin. > > >-------------------------------------------------------- Eurolife Assurance Group plc, Eurolife House, 16 St John Street, London, EC1M 4NT Tel: 020-7454 1151 Fax: 020-7454 1277 www.eurolife.co.uk Registered in England, number 2471313 This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore, we do not accept responsibility for any errors or omissions that are present in this message, or any attachment, that have arisen as a result of e-mail transmission. If verification is required, please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.