I'm on digest, so sorry for the delay. Indexes on UniVerse and UniData are different. UniVerse will stop you from creating them if the file is open by any process (very good!). UniData will go on it's merry way and create the index even if the file is open by another process. You run the BUILD.INDEX command and all looks fine. Then you add more records to the file and the index appears broken. Your new records are not accounted for. On UniData, you must be absolutely sure that the file is not open when you create the index. On unix, I use "fuser -u [path to file]". I do not know the equivalent on Window$. Indexes have become very stable and accurate if created properly. As mentioned earlier, best not to use "I" or "V" dictionary items, if possible (especially TRANS or file OCONV's), and better to use the key and null in a boolean expression (using NO.NULLS at creation) instead of a "1" and "0". Just my 2 cents...
Shaun ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
