What about putting the variable change in the Report INIT? That's only executed once....

Barbara

>Hi Gino,
>I am sorry but my point is still valid as you move to a page
>the report is completly recalculated (up until to the page you want
>)
>so it will be resetted even if you don't return to the first page
>
>
>Arnon
>
>>
>>Actually, if you look carefully at Valerie's idea, you'll find that it
>does
>>work 100%
>>of the time...
>>
>>The Title band is only executed ONCE at the beginning of a PRINT or the
>>beginning
>>of a PREVIEW
>>
>>If the user wants to PREVIEW, we set glPrinted=.T. .. If they just
>>preview, the
>>title band will run once, setting glPrinted to .F. If after they view
>the
>>preview
>>they click the Print button (which can only be done once), glPrinted is
>set
>>back
>>to .T. (You could also use something like gnPrinted = 0 and increment it
>>in the
>>title band and check the count.)
>>
>>If the user PRINTS, we set glPrinted to .F., and it is toggled once to
>.T.
>
>>I haven't
>>tested what printing more than one copy does, but I'm hoping it generated
>>the form,
>>then prints the multiple copies.
>>
>>So Valerie, you look like you're in the clear!
>>
>>
>>
>>>I've found no way to trap it - finally I just removed it from the
>toolbar
>>>(for places where it matters)
>>>
>>>Arnon
>>>
>>>>
>>>>I am finding it hard to believe that our old Big Brother MS has
>provided
>>us
>>>>NO WAY to tell if the Print button was pressed on the Print Preview
>>>>toolbar. Maybe there's a way to trap the event by going to the API?
>>Any
>>>>suggestions?
>>>>
>>>>
>>
>>