>>>>Now I actually realised that it is no longer in memory as an object at all. What I am trying to get rid of is datasession that session object created and used.
>>>>
>>>>Any sword for this knot ?
>>>
>>>Make sure that all the aliases in that DS are really closed, =tablerevert() them as needed (or all the buffered ones). Happens in the command window - I can imagine it would happen in runtime as well. We're actually pampered by VFP's doing this sort of garbage collection for us, closing the tables for us when we quit.
>>
>>I am doing it before trying to release (kill) session objects.
>>No buffering is used these are all tmp cursors. And they do get closed
>>but session itself is dangling :(
>>
>>CC Naomi;
>>Destroy method does not happen unless I issue more harsh stuff
>>such is 'clear all' , but that is in this case unacceptable.
>>
>>I have to enforce releasing partcular session object among others
>>which are to be kept without killing it all.
>>
>>I will try to destroy (and then recreate) entire array that holds them
>>to see if anything changes
>>
>>TIA
>>Sergio
>>
>>
>>
>>
>>
>>
>>
>>
>Calling Destroy() method directly (or release method directly) works?
>
>E.g. array[i].Destroy()
> array[i] = null
>
>?

Tried all / Did not work.

I am going now analysing all the way trough to see if something else got attached holding objects that I overlooked...