The important general idea is this:
Use the @-buffer to get the result of the i-desc calculation from the
*previous* record to apply it to the calculation for the *current*
record. (RetrieVe inits @-buffers to null (which goes to 0) when the
sentence executes.)
I don't think this works for
> From Martin's response, I'm guessing not for QM, either.
In QM, the @1, @2, etc variables are simply local variables within the I-type
expression. This gives us the useful advantage of
being able to nest compound I-type but does, as you suggest, prevent their use
to retain values across uses o
Although we think the Universe and Unidata market does not understand the
importance of monthly updates let alone weekly updates, we think we do at
U2logic. We are adding features and enhancements as fast as we can to our
XLr8 Tools products. We have just finished these for our 3.8.1 release:
