Subject | Re: identifying where an IB script fails |
---|---|
Author | Aage Johansen |
Post date | 2001-10-24T20:32:49Z |
Mark Meyer wrote:
sufficient.
Otherwise, you could make a small application with IBO's script component
(if you are using Delphi or BCB).
Here is something from the help on TIB_Script:
This component allows multiple consecutive DML, DDL, etc. statements to be
executed sequentially. This is very useful for creating database files or
for performing batch updates.
During the process of execution if the API returns an error code the
OnError event gives an opportunity to override or handle it and determine
if execution of the Script should continue or not. To examine the statement
that caused the error check the CurrentSQL property.
It is also possible to provide custom handling per each individual
statement that will be processed. Use the OnStatement event for this.
Regards,
Aage J.
cc: Mark Meyer
> Question:You could try IB_SQL (from www.ibobjects.com)- maybe the error reporting is
> what is the best way to identify where and why an IB script failed when
> running it inside of either ISQL or WISQL.
> ...
sufficient.
Otherwise, you could make a small application with IBO's script component
(if you are using Delphi or BCB).
Here is something from the help on TIB_Script:
This component allows multiple consecutive DML, DDL, etc. statements to be
executed sequentially. This is very useful for creating database files or
for performing batch updates.
During the process of execution if the API returns an error code the
OnError event gives an opportunity to override or handle it and determine
if execution of the Script should continue or not. To examine the statement
that caused the error check the CurrentSQL property.
It is also possible to provide custom handling per each individual
statement that will be processed. Use the OnStatement event for this.
Regards,
Aage J.
cc: Mark Meyer