You are right :)
Well, I did not think about this posibility 7-8 years ago when I was shaping up my VFP reporting. Even now when I tried it, I was curious what call to _vfp.SetVar() will return, but since it returns empty string this is defenately better way to go :)

I will hv to live with this kind of overkill for quiet a while, since I hv one function like this doing this job for hundreds of reports.
It would kill me to kill overkill :)

Thks Sergey :)



>It's overkill to create a function just to set a variable value. It can be done with an expression

_VFP.SetVar("report_end", .T.)

>
>>Solution I use goes like this;
>>
>>1. Add report variable called 'report_end'
>>2. Add report expression to summary band of your report calling
>>folowing function ;
>>
>>

>>function end_of_report
>>    report_end=.t.
>>    return ''
>>return .t.
>>
>>

>>
>>So report field placed in summary band should have this (call) as expression ;
>>
>>

>>end_of_report()
>>

>>
>>
>>Since function returns '', nothing will show on the face of the report,
>>while desired variable will be set to .t. after last record.
>>
>>3 Put invoice total in page footer and print only when that variable is .t.
>>
>>clause printwhen :
>>report_end=.t.
>>