Hi Tom ---

I think you might want to consider using the default datasession in all forms if you are going to be creating your cursors from the default datasession and outside of the forms.

Either that or ...hmmm....maybe convert your SPT stuff to an ADO recordset object. This way the datasession stuff is irrelevent.


>I have a problem with a lingering datasession. The default
>datasession is level 1 and the private datasession is level 2
>but level 2 does not go away after the form completes.
>
>I am using VFP 6 and under the default datasession I am
>instantiating a SQLConnect object to Oracle. Once an
>event occurs, I kick off a form with a private data session
>(session 2) that I would like to use the already active
>SQLObject. In order to return the data to the correct
>datasession (session 2) I passed in the calling form's
>datasessionid to the SQLObject.
>
>The problem is that the private data session (level 2) is
>still around after the form closes. Why? I thought if
>I simply copy the form.datasessionid to a VFP variable and
>just passed it that there would not be any lingering
>reference.
>
>I would expect for datasession level 2 to close itself once
>the form with the same datasession is no longer active. Any
>ideas on how to rectify this situation? I want the SQLObject
>to instantiate in the main program because it is slow to
>bring up and should be available to other forms that need it...