Subject | Re: [IBO] RE: Datapump action |
---|---|
Author | Jason Wharton |
Post date | 2003-10-08T20:25:11Z |
I don't know off the top of my head where to do this. I suggest you trace
the code and see if any opportunities present.
If using a dataset as the destination, perhaps in the BeforePost event?
If using a TIB_DSQL then try using the BeforeExecute event?
Jason Wharton
the code and see if any opportunities present.
If using a dataset as the destination, perhaps in the BeforePost event?
If using a TIB_DSQL then try using the BeforeExecute event?
Jason Wharton
----- Original Message -----
From: "Riho-Rene Ellermaa" <r.ellermaa@...>
To: <IBObjects@yahoogroups.com>
Sent: Monday, October 06, 2003 1:49 AM
Subject: RE: [IBO] RE: Datapump action
> <At 10:21 AM 6/10/2003 +0300, you wrote:
> >>Also, where is it possible to modify the Destination dataset's value for
> >>some records?
> >>At first I thought that AfterFetchRow can be used, but all my changes
are
> >>overwritten with original values.
>
> >Why use a dataset for the DstStatement? Use a parameterised TIB_DSQL and
> >put any data-massaging code into its BeforeExecute event.
>
> >Helen
>
> I must pump 30 tables and to make things easier I use TIB_Cursors.
> I have stringlist with tables names and while looping, I create
> "SELECT * FROM " + Tablename[i]
> for source and destination cursors.
> It works fine, except this modifying problem.
> I tried to use BeforePost on destination cursor, but I can't see any
values from there and my modifications are overwritten.
>
> IMO the AfterFetchRow should allow user to make necessary changes.
Currently I can change only new fields that didn't exist in older database.
>
> I dont kow if this is a bug or not, but if in destination database I have
field that can't be NULL, but in source database it is NULL, then I get
error (Field cannot be NULL) even if I supply the value in AfterFetchRow.
>
> Riho-Rene Ellermaa
> senior programmer