Well, I seem to have painted myself into a corner with this one. I have coded an application with 1 to Many parent/child relations going six deep. Each relationship is using internally generated key fields.

Now, my client (internal) is asking for the capability to copy a relation tree from the top down to a new record - with it's own copy of all the children, grandkids, great grandkids, etc.

No doubt this is a common situation - and I'd like to know how you folks handle this situation before I scratch a hole in my cranium right down to the medulla! I suspect I'm gonna have to work from the bottom to the top, using a temporary lookup table to map new ney fields to the old ones so I can keep the relationships straight....

TIA for any advise.