Thanks, all. A few things I've observed: 1. It doesn't matter what type of command is being EXECUTEd; the problem persists. I've tried the suggestions here, plus unrelated commands such as "DATE" or "WHERE". It seems that anything EXECUTEd will cause the ID to be lost because the process is, I believe, shelling out to another environment.
2. The XLATE function would be great since it doesn't involve shelling out to another environment. However, it requires that I know an ID in TRADES that has a CODE_DEFS id in the TRADE_CODE field. Instead, I need to search for such an ID. 3. The SETINDEX seems to hold some hope, since it doesn't shell out and it gives me the answer to the question, "Do any records exist with such-and-such value in TRADE_CODE?" I'll give it a shot. Thanks for all the suggestions so far. I'll let you know what the results are. Jonathan -- View this message in context: http://old.nabble.com/Very-Weird-Trigger-Behavior-tp31450305p31451269.html Sent from the U2 - Users mailing list archive at Nabble.com. _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
