Mark,

I have a new problem with my report datasession I wanted to bounce off of you or anyone else out there.

Here is the senario.

I start up my app and open a form using a private datasession before I run my report. I then run the code below to create my cursor to be used by my report.

This report is using a private datasession and in the datasession.init I run the code you provided in your previous response to determine the datasession where my cursor was created so I can set the datasession and select the cursor. In this senario the datasession always winds up being default(1) and everything works.

However, as soon as I run a different report the cursor gets created in the private datasession of the form and I'm unable to select it so my report blows up.

I'm trying to determine how I can force the method used to create the cursor to use the default datasession everytime or create a new private datasession, but with no luck. Is this possible to do?

Keith


>I have a VFP report using a private datasession that I execute as follows:
>
>public oFilters
>
>oFilters=NEWOBJECT('reportsfilter','appfilters')
>oFilters.rpt_closure_key()
>
>REPORT FORM CURDIR()+'report\&gcReportName'
>
>
>.rpt_closure_key() is the method that creates the cursor "proposal" used by the report.
>
>
>My question is, how do I tell the report the name of the cursor to use. I can't add it as a table in the data environment. In the report datasession init I tried adding:
>
> set datasession to 1
> select proprosal
>
>That works if nothing else is open, however, if I have a form open first then the report doesn't use datasession 1.
>
>Keith