>>Dragan,
>>
>>And note that the speed of XML drops squarely with its size. It being a text file, it just has to be parsed; the speed of parsing is beyond our control. So for larger datasets you may actually be better off with a temp table, or a collection of scatter name objects (and the dangling DS should be possible to solve by tablerevert()ing every cursor it has).
>>
>>Hi. How can a dangling DS happen in the case doing a collection of scatter name objects?
>>
>>Pardon my ignorance if this is a stupid question.
>
>Never happened to me that it could prove the scatter caused anything. Just mentioned it because others (Tamar, I think) said it's possible.

It's easy to test - did so last week

If form B has a private datasession
- it creates an object (other than the onces that have private datasessions)
- then puts that object in Form A
- then releases

you will see an unknown datasession, that will disappear as soon as you set the object in form A to null