>George,
>
>I've been getting around the problem by calling all reports through a REPORT Class originally because of the _FPRESET work around to solve the HP Printer lockups in VFP 6.0 since the fall of 1998. I just added it into the class right away as well to strip out the TAG and TAG2 info on the fly. That way any user defined reports also get that info cleared out as well.
>
>I also modify the placement of my reports on the fly though too for adjusting to match pre-printed forms to various printers by adjusting all of the X and Y coordinates for all objects on the fly then printing the report. So I call the report class with the report filename and an X, Y offset if necessary which then places it on the page with the offset.

You're saying that I should add E?< s > First, Rich, I understand your position and what you've done is probably exactly the right approach. Still, there's something to be said for a smaller code base and/or the ability not to have to worry about it.

Thanks for the feedback.