IBM could help us here by writing a backward link in the I_INDEX.MAP that says where the primary file is that the index supposedly references. If there is a mismatch, error out.
Is there a situation where the current state, where more than one primary files could point to the same index is a "feature"? cds -----Original Message----- From: Martin Phillips Sent: Wednesday, July 28, 2004 2:28 PM Another trap for the unwary.... If you use an operating system copy program to move a UniVerse file that has alternate key indices, the index subfile pathname stored in the file header will not be updated. You may need to use SET.INDEX to correct this after the copy. I know of one major UV user who copied a file to a test system in this way and later discovered that updates were adjusting the indices on the live system across a network. I never heard what this did for their business! ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
