Posted by Grant Foraker on May 29, 2018 at 10:15:34:
I have a WDL program with COMBO.01 that contains a list of jobs. When COMBO.01 changes a series of GOSUBs is invoked that load the various controls with pertinent information and loads COMBO.02 with the items associated with the selected job.
For local Comet users this has worked fine, but some CAW users maybe arrowing down COMBO.01 invoking multiple sets of GOSUBs. Usually, the GOSUBs catch up (you can see the screen blink thru repeated displays). But, sometimes the GOSUBs get tangled and an E32 occurs. Because a key is built from COMBO.01 and COMBO.02 that is invalid.
Is there a way to track the GOSUBs so I can RETURN out of earlier ones and just let the latest complete.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.