Subject | [IBO] Re: further understanding of transactions in IBO |
---|---|
Author | Scronkey |
Post date | 2002-09-05T23:40:14Z |
OK, will try this, but I'm still unsure of how the sp should be set
up.
The table I'm importing into has 21 fields, and I'm not sure whether
this is a good thing, to have an sp with 21 input parameters.
If this is what I should be doing, then do I use the DSQL, accepting
parameters (fields from BDE table), then pass those params onto the
sp (using EXECUTE PROCEDURE)?
Sorry if this is a little vague, it's just that I'm not overly
familiar with sp's and not sure of their limitations.
-Ryan
up.
The table I'm importing into has 21 fields, and I'm not sure whether
this is a good thing, to have an sp with 21 input parameters.
If this is what I should be doing, then do I use the DSQL, accepting
parameters (fields from BDE table), then pass those params onto the
sp (using EXECUTE PROCEDURE)?
Sorry if this is a little vague, it's just that I'm not overly
familiar with sp's and not sure of their limitations.
-Ryan
--- In IBObjects@y..., "Jason Wharton" <jwharton@i...> wrote:
> 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.
>