>[snip]
>>Documenting the code in the wrapper is a plus, but then it should be an absolute rule that all reports are run trough the wrapper, otherwise it may still be a little puzzling what the myVar represents in the report.
>>Not as easy as I wished...
>[snip]
>Doru -
>ok -
>extend your wrapper a bit - Lisa's method absolutely does a two pass report run. First Pass is to get the total number of pages - the 'M' here in your original post, represented in her CODE as 'myvar' . Don't like 'myvar' ?
>Call it something else - its just a pseudo variable name at this point anyway.

That much I understand.<s>

>
>But plan for your wrapper to do the first pass, regardless of any of the output options you may be 'trapping' there in your wrapper.
>
>wrappers are cool - make this one more 'generic' to handle your page counts .
>'wrap' your head around it some more, and see if you actually have an entry point to do some code changes..

One problem is that many reports are not run from a wrapper that presets myVar to the right value. Also the same report is sometimes run from a wrapper, sometimes not. In our page() prg, we could test for the existence of myVar, and avoid an error, but then users will get "page 1 of 15" sometimes, sometimes only "page 1". I guess I wanted _pagetotal to behave the same as _page, and not go into if or why it is impossible to implement.


>hth - mondo regards [Bill]

Thanks.