I guess this was what everybody was recomending. But if the OP for whatever reason decides do work otherwise it is not up to anybody to teach him about this.

I have a datasession that is separated from any other form but gives a dataset I need in mostly any other form. I can choose to run anything in just one datasession, or do something to move the data around.


>Wow. How about doing nothing and getting the best speed? Have the called form adopt the data session of the calling form. 3 lines of code. Talk about overkill and waste.
>
>>>I noticed that the debugger did not support peeking into the collection at run time - I usually like to take a look the first time I run something to see if the data looks okay. So I had to write a bit of temp code to iterate through the collection throwing each item into an object so I could take a peek. But overall, I like the concept.
>>>
>>>Albert
>>>
>>
>>Hi Albert:
>>
>>If data to be passed is flat (records) and not complex (hierarchical records from different tables), and for fast performance, you can use simple arrays that can be created with Select-SQL, or even can passs arrays (one or more) attached to an object, so you can pass the object reference and from that you can show directly the array data or generate a cursor with INSERT FROM ARRAY syntax. This way you can avoid the complexity of collections and can debug directly too. Arrays are faster than collections.
>>
>>On the other side, collections of record objects have the adventage that you can reference the fields by their names, and not by their column numbers, like when using arrays, but for more than a few hundred of records arrays are faster.
>>
>>Best regards.-