Hi Diana,

>I'm having trouble with a reference hanging out there on a form, leaving a private datasession open after the form is closed.

As far as I know, Form's DataSession has nothing to do with other form's datasession specifically if set to private because it is exclusively an attribute of the form. Once the form is release, datasession for that form or formset or toolbar has released.

Anyway, where did you issue RELEASE THISFORM or Thisform.Release()?

>>>>I call the form with a DO FORM (tried both NAME clause and without)
>>>>
>>>>Tried calling it from oApp.DOFORM() (Similar to TazTraders)
>>>>
>>>>I exit the form with a thisform.release(), and I tried RELEASE thisform.
>>>>
>>>>None of these gets rid of the pesky Datasession.
>>>>
>>>>In my app cleanup code, my CLEAR ALL runs through the destroy method of the form's objects, and it's not happy. I get a Dr Watson every time.
>>>>
>>>>Help, anyone ?
>>>>
>>>>Thanks !
>>>"Clear all" is dangerous I think. Instead in your form.de, set autoclosetables = .t.
>>>Cetin
>>
>>Cetin -
>>thanks for your reply, but by the time I issue the CLEAR ALL, the datasessions are supposed to be gone. It's a final clean up. (As recommended by MS, but we all know how risky those recommendations are...)
>>
>>Anyway - I do have the autoopen and autoclose both set to .T.
>>The Datasessions are still hanging...
>Hi Diana, I'm a bit inexperienced in all this but (therefore?!) had a similar problem when I was using a combo box to trigger a form change. Looks nasty but the user wants it that way. Anyway I had code in the "valid" method and it was just awful. Moved it to the lost focus and click methods with a few changes and it came right. You are using a button so that shouldn't be a problem but just have a play with the placement of your code, check your table buffering etc and hopefully it'll come right.
>rgds Sarah