>>Jim,
>>
>>PRIVATE to what?
>>To the calling code that calls the report? This will now work under all circumstances. I have a wrapper to the report call. I create all Data I need to to the report and call the wrapping code (creating listeners, chainging reports, controls page numbers etc).
>>
>>Anyway, do I missunderstand something? My idea of PRIVATE was that the private statement declares that some vars should NOT be used from the public pool.
>
>Yes, but that's not the whole story: any such variables, if assigned (and PRIVATE declaration does not create them, unlike public and local, which do) will be visible in the called code, which includes the reports. Local are absolutely local; private are shared with the code lower on the call stack.

Ah, I see.
So half of the wonders of public vars will work too? I stick with properties of _screen ...

Update:

O.K. _SCREEN is a public var, isn't it?

Agnes