Dennis & others, I had to step away for most of the day so just got back to your suggestions. I believe you may have hit on something, Dennis.
The only machine this is happening on is a VISTA machine using an older laser printer. I have thought for some time that it is more of a memory issue. If the two (computer and printer) are communication too slowly, then maybe the printing is not finishing prior to the CLOSEWINDOW. If the spooling is not fast enough, I can see how that could be the case. The printer has 64M of ram but these days, that may not be enough. When I run the same form on my machine, I have not had this problem. Also shipping has told me the reports come out VERY slooowly. I have run RSTYLE and everything is fine there. Is there something else I may be missing? This will be good information for my lobbying for a newer computer for shipping. Jim -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath Sent: Tuesday, April 09, 2013 8:46 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: CLOSEWINDOW Your CLOSEWINDOW is in the right place. CLOSEWINDOW will not work if other code is still running. Did you RSTYLE the code? Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Tuesday, April 09, 2013 7:19 AM 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
