Aaron -

To be clear, there is no way to prevent this happening?!

I thought my previous replies would have answered this, so obviously I am not understanding your question.

I will agree that the behavior of .OutputPage(n, oRef, 2) is a bit counter-intuitive. It does not "draw on the foxpro object" referenced by the oRef parameter. It draws on the FORM. (or the SCREEN if the oRef is a child of the screen rather than the form.

It also does this outside of the usual buffered graphics used to display controls, hence the overwrite effect.

That's the way it works. My article describes a way of working around this.

I will confess that I have not tried using a target object that is in a page frame, so perhaps you are seeing some different effect than that I describe here?

- Colin