Wally Terhune-2 wrote: > > Uh, don't grant your users ECL access? :-) I've often said the computer system would work fine if we could keep people off of it.
Wally Terhune-2 wrote: > > Feel free to submit this request via your U2 support provider. Not sure > how easily it could be accomplished, but we will give it consideration > when it percolates up to me. Certainly nothing we would fix at your old > release level (6.0.unknown) - even if we could. Unfortunately, the company I'm contracting with has no provider relationship. Is there any way we submit it directly? Wally Terhune-2 wrote: > > Ps - we recently worked with something similar regarding these global > variables, but at first glance - it seems likely to be somewhat different > than your situation: > > Addressed at UniData release 7.2.7: > Issue 12476 - Problem Description > > UniBasic -- If a UniBasic subroutine was called by a virtual field, > the value of the @ID may have become corrupted. The @ID value was > changed to the last key of the file if the subroutine used the > EXECUTE command to perform a SELECT of this file and used a WITH clause. > > For this problem to occur, at least two dictionary items calling a > subroutine that included the @ID as an input argument had to > be present in the SELECT statement. > > This problem has been fixed. Hmmm. It certainly could be related, since the @ID and @FILE.NAME variables available in virtual fields certainly reference some deeper environment variable in the Unidata shell. Thanks for the enlightenment. :) -- View this message in context: http://old.nabble.com/Very-Weird-Trigger-Behavior-tp31450305p31452195.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
