Thanks Ed,

> the child form using Default Datasessions inherits the same datasession as the parent form - if the parent form is using a private datasession, the child report using default datasession will share the parent's private datasession as a result.

Guess my mistake was in thinking that a PRG called from a MENU could set it's data session to 1 and get THE default dataSession. You've helped clear things up for me.

I am switching things around, to have a hidden report form, w/a Private datasession, that calls the prg. Obviously, things could be done in a much better way (moving the PRG code to form methods, opening only tables needed, etc.), but it's not my project, and this will work for now. I'll improve on it in my own projects in the future.

> Is there some reason to run the report in the default datasession? Using private datasessions has been (for me at least) far less prone to accidental side-effects from having tables autoclosed because of carelessness on my part, but that's likely a matter of the coding style I use to build VFP reports.

Just getting started that way, for reports, a few years ago . . .habit, not rethinking things through as I learn more, etc. I make widespread use of private datasessions in other areas.

Thanks again for your help.

J