TCRBatchMove workaround
Posted: Tue 23 May 2017 15:48
Hello,
Using UniDAC 7.0.2.
As far as I know TCRBatchMove identify primary key in a TDataSet automatically. I would like to know if there is any way to provide primary key columns manually.
I am using TCRBatchMove between two detail tables. Both detail table's primary key is set on an autoincrement column. I would like to define TCRBatchMove to use two columns where second column is master link column. This will help me get rid of wrong append/update of records between source and destination because of different autoincrement column values in a multi-user environment.
Thanks.
Using UniDAC 7.0.2.
As far as I know TCRBatchMove identify primary key in a TDataSet automatically. I would like to know if there is any way to provide primary key columns manually.
I am using TCRBatchMove between two detail tables. Both detail table's primary key is set on an autoincrement column. I would like to define TCRBatchMove to use two columns where second column is master link column. This will help me get rid of wrong append/update of records between source and destination because of different autoincrement column values in a multi-user environment.
Thanks.