>>Hi,
>>
>>I am considering a feature for my app that would allow user combining two records into one. For example, say in the parts table they have two pars "1234" and "1234A" and at some point (after years of use) they realize that this is one and the same part. They can't rename one into the other because another record of unique entry already exists. They can't delete one because it has child records (transactions, P.O.s etc.). So I am thinking of writing a routine that would do it in code. Does it make sense? What I mean is, do others (as other developers on this message board) have routines that allow combining two records with different values in unique field into one? TIA.
>
>
>Just be VERY certain that those 2 records were identical in history as well -
>which depending on the data schema utilized may not be clear to the operator.
>
>If that cannot be asserted, a trick is to add a new ID field to the duplicate record to be used in all
>new transactions (pointing to the ID of the "original" record) which will be used if not NULL.
>
>Makes sure all new data is clean and all the history with perhaps differing price info for those 2 IDs is kept.
>
>regards
>
>thomas

Thank you very much for helpful suggestions.