I like this idea, except that a lot of the reports are not run from a form, they could be run from a menu or run from a prg or believe it or not, an .spr which is run in the app. A lot of the FPD26 screens have not been converted to forms yet so they are in the app as .sprs and actually run that way in the VFP7 app. Can you think of anyway to do that using prgs (since .sprs are actually just like prgs)? That might work for me. I guess I could create a print form that is hidden and has the embedded IEBrowser control on the form and release the form when it is finished printing the html document? Any examples of code to do this? I haven't played with the IEBrowser control at all believe it or not (well when VFP7 first was released I did, but I no longer have that code)!

Tracy

>Hi Tracy,
>
>>Let me know if you come up with a good solution
>
>>I had to do them all manually, one by one, and we still have hundreds of
>>them to go! Yuck!
>
>Another way to go is to display them as HTML documents in an embedded IEBrowser control in a form. Luckily for me the reports are all written for "courier new" and the escape sequences are held as memory variables (which can easily be changed to HTML formatting tags).
>
>Of course the downside is that printing from the IEBrowser control is very slow.
>
>Hugh