Hi Garrett,

>>So far the below works!!!!! I'll test in the app today...
>
>There are two (update: 3) things I noticed.
>
>First, you're saving and changing the screen font in the wrong order.


I don't understand. What is the right order? Basically, I am emulating strange errors that occur in our app hapzardly. We have a VFP7 app that is HUGE and actually runs some older FPD26 screens in it. If one of the FPD26 screens is currently displayed and the user prints an older report that uses @...say and sends escape code sequences to the printer to change the font, *SOMETIMES* the fonts are changed on the screen as well. Also, if the screen colors are not black on white because the older screens set the color using set color to ... then the report will print out with a shaded background. To correct this, we are changing the screen color (or creating a temporary window with the correct screen color) to black on white and then correcting the font and screen color (or releasing the temporary window) when the printing finishes. We are trying to do this without the screen flickering or clearing reliably.

>
>Second, why bother? You're just throwing this away when you're done, right? :-)

Nope, I plan on incorporating the pertinent fix to the app.

>
>Third, why does that work? If you're changing the screen font and color in the other instance of VFP, why are you able to print from the current instance of VFP using the new settings?

You got me! I have no idea...