Keep in mind that the index gets updated when the PRIMARY file gets written to disk. If the value of the translate changes (because the secondary file gets updated), the index will still be loaded with the old value. This is not a bug. That is just the way it works.
For example, let's say you had a SALES.ORDER file (primary) that stores the CUSTOMER.ID as one of its field. In the CUSTOMER file (secondary), you have a field called CREDIT.STATUS. Next, you have a translate from the SALES.ORDER file going to the CUSTOMER file to return the CREDIT.STATUS of the customer associated with the orders. No problem so far. Next, you add an alternate index to this translate. At that moment, everything is fine. However, if the CREDIT.STATUS for a customer changes, the alternate index (translate) in the SALES.ORDER file will not know there is a change! Any alternate indexes on the CUSTOMER file will be updated because the CUSTOMER file was written to disk. Since the SALES.ORDER file was not written to disk, its alternate indexes remain unchanged. Thus if you select all the SALES.ORDERs with the customer's CREDIT.STATUS = "1", you will get the orders whose CREDIT.STATUS WAS "1", but may not be any more. If you are confident that the value of the translate will not change, then you should be OK. John -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Bullard Sent: Thursday, June 28, 2012 7:31 AM To: U2 Users List Subject: Re: [U2] Regarding: use of I - Descriptor "You can even put alternate indexes on I-Desc, though this can lead to serious problems if you are indexing a translate." I read this comment (from an earlier thread on this list) and started worrying: I have a requirement to select records based on a field that is not currently in the record. I have been planning on creating an I-Desc that uses a TRANS() function to look up the data and then building an index on that field. What sort of "serious problems" would I expect from indexing a TRANS() I-descriptor? John B. This message and all attachments are intended for the use of the individual or entity to whom or which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure. If the reader of this message is not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify me immediately at the number listed above. U.S. export law as contained in the International Traffic In Arms Regulations (ITAR) and the Export Administration Regulations (EAR) may be applicable to any technical information submitted with this communication. This technical information is not to be placed in the public domain, exported from the U.S., or given to any foreign person in the U.S., without the prior, specific written authorization of TeligentEMS LLC and the U.S. Department of State or the U.S. Department of Commerce as applicable. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users