>vfp screen is a curious object.
>it cannot be scrolled and the vfp designers say in foxHelp:
>scrollbars property is ignored by _screen object.
>
>if you issue a small test code
>

>for i=1 to 1000
>?i,cos(i)
>endfor
>

>
>you see the result (behind the command window but troncated and not scrollable to read all datas!
>
>1.why all these when we know vfp objects have scrollbars(custom windows (define window),form,editbox,grid....)
> is there historically a reason ?
>2.is there a solution to add scrollbar(s) (vertical, horizontal or both) ?
>Note: result of operation can be redirected out to a txt file or something else.....not concerned by my question.

Works the same if you activate a form and issue ? commands in it, or use form.print() method - the output goes to the background of the form, which is not really an object. Any refresh() will erase the output.

Historically, this kind of output is a console output, just like it was in Foxplus - where you had a command line and whatever you typed there, plus the results of ? commands and Set Talk would scroll up. There was no way to reach for that content above the command line and grab the content, unless you had it echoed into a file. Starting with FoxPro 1.0, the command line was moved to a command window, where you could scroll up and edit a line (which would still be copied to the current line before execution) but the output still went to this console space - which is behind any windows and never survives a CLEAR or refresh (but objects do).