This app uses the document-response relation between documents, the problem is that documents (and its responses) that have been generated in one DB loose their relationship when copied to a second DB. What we have seen is that the UniversalID of the main document changes in the second DB and so should the $Ref field on all its responses, but the problem is that the responses maintain the old value (the UniversalID of the parent in the original DB).
Subject: Parent & response documents loose their relationship when copied from one DB to another
How are you copying them? If you do a simple copy and paste, making sure that you do both parent and responses in the same operation, the response hierarchy will be maintained.
Exactly thats the way we are doing it, with a simple copy and paste, both parent & response in the same operation. In fact this operation has no problem when the documents are copied from any other db, this problem is only present when copied from one particular db who is a new version of an app created in R4, then migrated to R5, and now modified and copiled in R6, so its very mature in its design and never before had it presented a similar problem.
Subject: Parent & response documents loose their relationship when copied from one DB to another
It doesn’t work the way you think it does. When you copy a document to a new db, the universal ID changes without regard to $ref. The only way around this is to have a process to modify $ref (something that Lotus does not support but just about everyone does anyway)
But i had done this before, i mean copying and pasting a main document and its responses from one DB to anohter and they normally maintain their relationship, its only with this DB.