Steve, I've agonized over this one myself. My situation is very similar to yours. Lots of intermediate tables are generated on the way to a cursor that needs to be visible to other datasessions.

I have not found a completely satisfactory answer. One technique is to copy from your cursor to an array, as it will be visible across all data sessions. Another alternative (sometimes possible) is to avoid using private data session for some multi-instance forms, and instead give their cursors unique names in the default data environment. You will of course need to dynamically bind the controls to their data source(s) during the form's init. The only other alternative I have found is to slam the data into a true table, using it as a conduit for the private datasession. If you have a RAM disk on your system, you can copy to a table there.

>Private Datasessions - I need to get a cursor created in one private datasession to be "seen" in a different datasession. I cannot simply pass parameters from the first and create a view in the second one as the creation of this "final" cursor is derived from several intermediate cursors created in the first datasession. How to get the final cursor loaded into the DE of the second private datasession is the question.
>
>Thanks,
>Steve