Benoit,

Try changing the DW's Update Properties - to specify only "Key Columns" on
the "Where Clause for Update/Delete".  This would work then in your trying
to fake out the DW with the DataModified statuses.

I suspect that you have another choice selected, and so the where clause is
saying WHERE x=<"original" value> and the so-called original value (your
piped-in-import value) never matches the value in the actual table.  So the
update thinks that someone in the meantime has changed the data since you
last retrieved the data - since your original buffer has bogus data in it
that does not match the database.

Are you trying to update only a select SUBSET of rows of the table from a
flat file?  Otherwise it might just be easier and cleaner to delete all
rows (with either embedded SQL or with a retrieve/delete-all), and then
import and update.

Also, are you guaranteed that every row in your flat file is indeed already
on the database?  That would be another consideration if you still get a -3
after using only Key Columns in your update properties.

Have fun,
~Sharon
--
Sharon Weinstrom Buntz      | mailto:[EMAIL PROTECTED]
Cheat Sheet for PFC/PB Help | http://www.pfccheatsheet.com/


[EMAIL PROTECTED] wrote:
> 
> Chaps,
> 
> I need help.
> When I want to update a DW, I always have the following PB error code ( -3 )
> :
>    Row changed between retrieve and update
> 
> The DW is just a normal DW, I mean it has a SELECT statement, and it is
> updateable.
> The thing is that the SELECT MUST returns nothing, empty rows, nada, because
> its purpose
> is to update existing data in the DB, not to insert new data.
> 
> So, the DW is populated via a flat file using the function ImportFile (
> filename ). Then, I change
> the whole row status to DataModified! as well other updateable columns.
> 
> Any idea about this error message ?
> 
> Cheers,
> Benoit.
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE:   help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]

Reply via email to