>Hi srjdan,
>
>What about cursor that exceed the 64K array element limits. I think you'll have to count for that situation.
>
>Walter

Hi Walter, [Wld not mistype your name as 'Watler' as you did with mine :-) ]

At first, I tought that array limits are removed with VFP9,
but then when reading MSDN help I understood, limit still exist for arrays which are member of some object :(

I am curious however, how about NET ? No object array limits there ?

My take is that most of these session2session transfers are smaller recordsets so this faq still might come handy for meny or even most of common business cases. And I said so there anyway...

However, it wld be relatively easy to implement similar solution work with
'temporary public' arrays instead of member arrays but I don't think is realy necessary.

At the end of the day, for huge amounts of data there are always Cursor2FreeTable scenario available, where we can simply pass name/path
and then receiving session can simply open/consume it.
(CursorToXml wld be to slow for this as I hv heard)

So regarding moving data back end fourth,
I still don't think so that NET has it better then us :)