@MV and MV (AREV Specific)
At 03 JUN 1999 12:19:39PM Bruce Lee wrote:
Hello,
I have used MV and @MV in my symbolics. Both seem to have the same
result; however, inserting Arev.Common is required when using MV.
What are the differences, if any when using @MV or MV in a sysmbolic.
Which one is preferred.
Thanks Bruce
At 03 JUN 1999 01:41PM Warren wrote:
The main difference you'll find is that if you use AREV.COMMON and MV you'll get a "Variable not assigned" error if you try to use the symbolic in RList.
This comes from the AREV.COMMON.
@MV will always return zero in RList.
At 03 JUN 1999 04:07PM Don Miller wrote:
The difference used to be significant in AREV2.0 where @MV was not always set properly in AMV's in a window. This was fixed in AREV2.12 and subsequent. Remember, in templates, you can get bizarre repeating results in display symbolics, especially in Multi-Valued defaults which should always be single-valued and return the explicit value.
In R/LIST reports, AREV always sets @MV to zero - unfortunately!! This causes lots of slow AMV extraction and recalculation when using exploding multi-valued sorts. The Gen'd code uses READNEXT @ID,VALUE.NO … and then uses this. It would be nice to set @MV to equal value.no so a symbolic would work in both a report and the screen.
Don Miller