Tom,
You can put a report in your Project Manager but leave it out of the compiled EXE. Just right-click on the report in the PM and pick 'Exclude'. IF the compiling is affecting your report this will solve the problem - you WILL have to distribute the report with the EXE, of course.

You may wish to make the report files read only, as well.

Finally, you could even open the report as an FRX and check (or even automatically replace) the printer and font information before each use.

I hope one of these suggestions gives you an idea that will work.

Barbara
>Hi All!
>
>We have a distributed application that builds specialized printed forms from a client database. The report builder was used to create the report form and it was (for better or worse) included in the project. The form size is very specific and the printer driver and font is critical to keep the line printers from slowing to a crawl or not working at all.
>
>All is working correctly if the program is run interactively (within Foxpro command window). When the application is built into an .EXE file, the font changes to one that is not appropriate for the form, and the size of the form changes by itself. So, either the line printer wastes thousands of printed forms, or the app dies with an error about overrunning the paper size. After this occurs, I can reopen the report builder and it has resized the form to roughly 1/5 of its previous width.
>
>I've tried both hard coding the printer definition as a part of the program that calls the report form, and then removing that code and letting the report form do the printer setup. Both fail.
>
>What would affect the executable and not the interactively run program as relates to a report form?
>
>If you were developing an application that requires a specific network printer name, a driver for that printer, and odd paper sizes, how would you make sure the app and the computer both knew which printers/drivers to use. Current operating system is Win95 and Fox 5.0a as the development tool.
>
>TIA!
>Tom.