my solution has always been to test my upgrade scripts against a copy of the
database I intend to run it against. I iron out all script issues before I
issue it to the production databases

Alan

-----Original Message-----
From: Riho-Rene Ellermaa [mailto:r.ellermaa@...]
Sent: Thursday, 10 April 2003 7:08 PM
To: IBObjects@yahoogroups.com
Subject: RE: [IBO] Scripting problem


Thanks for hand-holding :)
This worked.

Another question on the same topic. I use TIB_Scripts to update my database.
Sometimes they contain lots of changes.
When some error happens in the middle of the script, then next time I can't
run it any more, because some changes have been commited and give
exceptions.
Is the only solution to put all commited changes into different scripts?

Riho-Rene Ellermaa
senior programmer
Hansabank

> Try to put a COMMIT after *each* DDL statement and re-run the
> script and see if
> that helps.
>
>

___________________________________________________________________________
IB Objects - direct, complete, custom connectivity to Firebird or InterBase
without the need for BDE, ODBC or any other layer.
___________________________________________________________________________
http://www.ibobjects.com - your IBO community resource for Tech Info papers,
keyword-searchable FAQ, community code contributions and more !

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/