Solution for CLOSE WINDOW after CONSTRUCT problem after <interrupt>

Thank you for the many replys which stated there was no work around to the problem I posted. But YOU WERE ALL WRONG hahahahaha (sinister laugh :-) ) To summerize, I received a error 1141 after attempting to execute a 'CLOSE WINDOW' statment following a CONSTRUCT that had been terminated with an interrupt. First prize goes to m.mejia@server1.codetel.net.do who came up with a solution that (get this Informix) actually works. Why this works, I have no idea. And get this, I don't care either. I have done some limited testing and it does appear to work. <begin code segment> FUNCTION getCriteria() .. CONSTRUCT .. END CONSTRUCT IF int_flag = TRUE THEN CALL closeInput() END IF .. END FUNCTION <end code segment> .. .. <begin solution> FUNCTION closeInput() MENU "" BEFORE MENU EXIT MENU END MENU END FUNCTION <end solution> Second prize goes to olded@ix.netcom.com which recommended using the ON KEY (INTERRUPT) to capture the interrupt and execute a CONTINUE CONSTRUCT. While this did not allow the user to cancel the CONSTRUCT, at least the program did not abort. Thank all for your input. John Callaway Bath Iron Works The information posted above is my own opinion and as such should be piped through sanity_check before using. Any side effects from the above code are solely your problem, or don't you believe in recursive testing???