>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.

Hi Dmitry,

I have the same problem in the POS/Inventory app I sell. What I did was give the users a form (see attached jpg) that allows then to select each of the products and then designate the one they want to keep. Then I have code that replaces the new primary key to all of the child records.

My solution is neither elegant nor generic because the code is specific to my data structure and, if I decided someday that another child table is needed, my assimilation code would need to be changed. But it works for me now.

Hope this helps,

Ken