NOPAGEEJECT at the end of the first REPORT FORM. But this will still cause an eject, if the reports starts with anything causing a new page, eg a page header of SlitJobPrn will print on a new page anyway, also group headers can be set to print on a new page. NOPAGEJECT is respected, but if the first element printed by the second report demands an eject, that also is respected and you get a nopageeject followed by an eject.
Following Olaf's advice, you would also have to take out the PROMPT clause on the second line. Better to use GETPRINTER() to find the user's choice of printer, and the SET PRINTER to that.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
I'd also drop the use of Locfile(). Just drop it from your vocabulary. It has a side effect you may not be aware of:
Code:
?Set("path")
Use LocFile("*.dbf")
?Set("path")
It adds the path of the selected file to Foxpro's search path. In most application environments the search path is something you want to set the way you want and not have it altered.
Another problem with LOCFILE(): If it can't find the file on its own, it displays a File Open dialogue. That's not something you would want your users to see. There would be nothing to stop the user choosing an incorrect or inappropriate file from the dialogue, or generating a "File does not exist" error.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.