Stevenson, Charles wrote: > The issue is this: the path to the index is hardcoded in the > header of a > data file. So if one uses OS-level, UV-unaware methods of > moving files > around, the wrong files point to the wrong indexes. Classic > example is > copying (cp, xcopy, etc.) a live file to a test area and the > test area's > version still points to the primary index. Both live & test files > update the same index. SET.INDEX command is the cure. > )
Does UniData not suffer from this problem? We copy files around all the time and have not seen this behavior. -- Wendy Smoak ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/