AREV window bombing on symbolic call (AREV Specific)
At 20 FEB 1998 12:07:28PM Laurie Young wrote:
I have a window (AREV 3.12) that uses a subroutine (catalyst) to bring in a selected piece of data (part number) from another file. After receiving the part number, subsequent fields are using a symbolic field as the default value. The part number brought in through the catalyst (popup) is the key to the related file/field.
This window works fine, as designed, *except* when the window is run from a menu. When the window is accessed from the menu, I get an error message stating that the first symbolic field cannot be executed because it does not exist in the dictionary. This symbolic is not related to the data supplied from catalyst.
After some debugging, I've found that all symbolics in the window fail (regardless of relation) when I press return to accept the value supplied by catalyst. If I remove the symbolic field, the next one fails and so on.
If this is memory, I can't figure it out since I have plenty of memory. The size of the field brought in by catalyst is only about 15 characters.
I'm confused. Any ideas?
At 20 FEB 1998 02:30PM Aaron Kaplan wrote:
I don't think the problem is a menu, but that it's run off a menu from level 0. Tough to explain, but fire up TCL, then run your main menu. Go through until you get the window. If the stuff still breaks, then you've got me.
If it runs fine then what you'll need to do is change your login so that your running the menu, preferably with an E to load up a new level.
I never really figured out why on some systems this is really important while on others it's not.
apk@sprezzatura.com
