At the start of the command file in the Bit button, I do drop the tables. I also set the error messages off. No error messages show up in the issue I mentioned. It is just that the form does not always close. Sometimes it does but not always.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tony IJntema Sent: Tuesday, April 09, 2013 7:36 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: CLOSEWINDOW As far as I know the EEP is executed totally. You can try it by yourself using set trace on Talking about trace, I often put this command in a bit button on the form when I am testing. Then you are able to switch it on whenever you like. Closewindow without specification will close the current form otherwise you should use an alias and as far as I know then the form has to opened as MDI. BTW why not dropping the temp tables just before the procedure is started. To avoid a error message in case they don't exist, you can use the statement set error message <nnnn> off Tony -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: dinsdag 9 april 2013 14:19 To: RBASE-L Mailing List Subject: [RBASE-L] - CLOSEWINDOW I have a form that does not always close after some reports have printed. These reports print within a WHILE LOOP. At the present time, the CLOSEWINDOW is the last line before the RETURN. If I put this command before my DROP TEMP commands will all those commands still work? In other words, will all the code after the CLOSEWINDOW command still fire all the way to the RETURN? These reports do eventually print but the users have to hit another button to clear the form. I just want the CLOSEWINDOW command to work all the time. James Belisle Making Information Systems People Friendly Since 1990
