Nope, the report runs in the same datasession as the form -- and it always sees the variables, it's just that some of them have the wrong (previous) values. In any case, I've given up trying to figure this out -- chalk it up as another unsolved mystery of report processing -- and I can work around it by submitting each record as a separate print job (it's one-record-per-page anyway), which is ineffecient, but at least it works. Thanks again for your help.


>Sounds like your report has a private datasession. Check that and change it to Default. Then it will see the private variables on the calling form.
>
>Barbara