>Cathy, (and anybody else who wishes to expound)
>In another thread you advised Winn (who was trying to print a continued... message):
>
>>I came up with a cleaner way to do this when I wrote the new Report Writer book...
>
>>... In the OnExit expression of the Data Group Footer, use _VFP.SetVar('nLines', 0) to clear the lines. Now you can put your "continued" text in the Page Footer band and use "nLines > 0" as the Print When expression.
>
>After reading the VFP help and Hackers Guide, my question is:
>Why is the variable nLines not 'directly' accessible, i.e. why are we treating it as a variable in 'another' application?
>
>When you were talking about this in Chicago last week, your comments on this must have passed through the space between my ears.... :-)
>

The variable nLines is directly accessible and _VFP belongs to the current VFP application. The reason we're using _VFP.SetVar('nLines', 0) because it allows to assign value to the variable in the expression field, like OnExit or OnEntry. Before that we would create a function that changes variable and put call to it into expression field.