I recommend using a TIB_DSQL component with an EXECUTE PROCEDURE statement.

Having the import operate via a stored procedure allows you to write a
simple program and then from there if changes are needed you have a point
where you can on the server customize what is taking place.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

-- We may not have it all together --
-- But together we have it all --

----- Original Message -----
From: "Scronkey" <ryan@...>
To: <IBObjects@yahoogroups.com>
Sent: Thursday, September 05, 2002 4:22 PM
Subject: [IBO] Re: further understanding of transactions in IBO


> Thanks for your reply Jason.
> For particular reasons, I need the entire batch to succeed or fail.
>
> But am I better off using a TIB_Cursor, or TIB_DSQL for this job?
> What are the speed / efficiency differences?
>
> Also, you suggested using a stored proc. By this, do you mean
> creating a stored proc which accepts all fields as paramteres, then
> execute the procedure?
>
> Rgds,
> -Ryan
>
> --- In IBObjects@y..., "Jason Wharton" <jwharton@i...> wrote:
> > That's exactly right. You were running in AutoCommit = true mode
> and calling
> > StartTransaction suspends AutoCommit and puts you in control.
> >
> > I highly recommend when importing data you use a stored procedure
> and
> > instead of failing a whole batch catch the exception for the
> record, log it
> > into a special errors table and allow the process to continue.
> >
> > See InterBase language guide for how to catch and respond to
> exceptions.
> >