Hello, all:

Figured why this particular DataPump would not work:
I need to drop the PK constraint first, otherwise since the old and new
IDs are close together during the UPDATE process, it is causing an
error, which for one reason or another the component wasn't catching,
but when I did a simple SELECT-WHILE NOT EOF-UPDATE it did catch it and
I recognized immediately what was going on.

Thanks,

Chuck


Chuck Belanger wrote:

> Hello:
>
> I'm using a DataPump component to update a table (Custom_View) of
> related IDs into a table called View_Type.
>
> The Source looks like:
> Select VT_ID, OLD_ID From View_Type WHERE OLD_ID is NOT NULL
>
> the DST looks like:
> UPDATE Custom_View SET VT_ID = :VT_ID WHERE VT_ID = :OLD_ID
>
> I've used this basic template many times without error.
>
> This time View_Type has the following data:
> VT_ID OLD_ID
> 114 73
> 115 114
> 116 115
> 117 116
>
> In my scenario, the current vt_id = 114 and should be replaced with 115,
> but instead its replaced by 117.
>
> Oddly, if I change the VT_ID numbers to almost any other sequence,
> everything works fine.
> I do clear the DSTLinks before running the pump.
>
> What gives?
>
> Thank you for any suggestions,
>
> Chuck Belanger
>
>
> ___________________________________________________________________________
> 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 !
> Yahoo! Groups Links
>
>
>
>
>
>