>Gregory's hint on save to memo will beat all other ways hands down in speed and in ease of generating -
>but reading out you will get the array back into a vfp array and you will have to handle that programmatically.
>Save to memo is a *great* way for vfp interprocess comm, but I am guessing that ascii-readability is better for your UC.
>
>Generating a whole row per line of code as Dragan suggests is one of the faster ways to do it - easy to code and probably fast enough unless you need it very often. But you could also create a cursor with the right structure, pipe the whole array into the cursor and output that cursor either as SDF
>(with for better "optical" reading and programmatic handling) or csv for space saving and easy import into excel or back into cursor. This ouput file can be easily read back by FiletoStr into the memo... So coding should be similarly easy and somewhere will be a cutoff point where this approach will be faster than working on each row appending to a char var - they get slower if the amount of data to copy over gets bigger. But I doubt speed should be a deciding factor here - but If you decide to measure speed across different stack lengths, post for lazy perf buffs like me...
>
>regards
>
>thomas

Hi Thomas,

A bit of hjacking the thread, but I have somewhat similar requirement and was thiking today of a best way to implement. In one of my forms I'm using a cursor to record some information. My problem is how to pass this information to the calling form. One idea would be to make that form share DS of the original form, but I have reservations - I'd like to keep this form using private DS. Passing XML doesn't seem a good approach. Using SD approach (I didn't re-check it) also seems a bit complex.

Your ideas of the best way of handling this?

Thanks.