Commuter Module Weirdness ({ } references) (AREV Specific)
At 04 OCT 2005 12:10:57PM Matt Sorrell wrote:
Okay, so I'm writing about the 10,000th commuter module, and this one is behaving quite strangely and I cannot figure it out.
I am adding validation and option processing for fields on a data entry window that has an AMV group of about 7 fields. Basically, the validation routine verifies that they entered a valid choice and that the choice is not redundant (a value can only be assigned once in the AMV field). The options routine starts with a list of all valid options, removes those that have already been used, and then presents a pop-up of the remaining valid options. It does this by using @ANS and referencing the existing record data using {field_name} calls.
All of this is working perfectly on the first field. For the second field, the {field_name} call is returning a null value. However, if I use @Record, I get the correct data. I don't mind using the @Record reference instead of the {} reference, it's just bugging me that I can't figure it out.
If necessary, I can post the code, but it compiles fine and works great if I change the {} refs to @Record refs. Also, I did make sure I was saving off @Ans when necessary so it wouldn't get stomped by the {} calls (that took me 15 minutes to figure out).
TIA!!!
At 04 OCT 2005 12:42PM [email protected] wrote:
Is @MV set?
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 04 OCT 2005 12:58PM Warren Auyong wrote:
Is @DICT set?
At 04 OCT 2005 01:29PM Matt Sorrell wrote:
I am not specifically setting @DICT or @MV in the subroutine. For some reason, I was thinking those would be passed in by the window.
I have switched all of my code to use @Record instead, and everything is working perfectly. I imagine that one of the @ variables was getting stepped on, and this has worked around the problem.