J
jquerijero
Guest
While diagnosing another mysterious lingering temp-table, I stumble upon this pattern; ON CHOOSE OF someButton: DEF VAR hTemp AS HANDLE NO-UNDO. RUN someprogram.p (OUTPUT TEMP-TABLE hTemp). RUN semeprocedure(INPUT TEMP-TABLE hTemp). /* this internal procedure has code to delete input temp-table handle per earlier discussion, and it works as you stated */ /* However in this scope itself, another copy is created. If I don't do this, a temp-table remains in the memory even after closing this window */ IF VALID-HANDLE(hTemp) THEN DO: DELETE OBJECT hTemp. hTemp = ?. END. END. Maybe the pattern can be pared down. Is this expected?
Continue reading...
Continue reading...