>Hi Cetin
>
>>There are many ways to pack and pass multiple parameters with data types. You've VFP6 SP5. You could write to a prg file at run time and compile it, put compiled code in 'bridge' table (or simply the code which is compiled on the receiving end). With this approach it looks like:
>>...
>>You can use now forgotten feature of Foxpro's ability to save and restore memory variables to .mem files. ie:
>>...
>>You can create an XML which receiver can read say with ADO.
>>etc
>
>I just found out what experience is all about.
>
>
>This is great. I like the prg idea, but mem is attractive too. Anyway in the morning session to get the table to be used the command
>
>USE (lcCursor)
>
>was creating problems since yesterday giving an error like 'c:\vso3\ssss\ddd\'c:\vso3\ssss\ddd\tempname.dbf is not found was solved by
>
>USE &lcCursor.
>
>and now I can use the file. I will get more into your suggstions, which is your favourite if variable type was the utmost important for you, precision and all.
>
>This is a great thread for me. Thanks.

:) Hmm I would first prevent:
use &lcCursor

and instead use:
use (m.lcCursor)
IOW trace why you get such a weird lcCursor value. You're still expnading the same variable and indirectly hitting & blues. Check what you really use with:
? dbf().

With & do not forget that long path names would cause troubles (some VFP commands hide this if it can fullfill the request using up to the first space).

"which is your favourite if variable type was the utmost important for you, precision and all"

This is really a hard question. I don't have one choice over all. I decide it depending on my needs. I like prg approach too and can use it with execscript() in later versions. Its side effect I have to code all probably in the place where it shouldn't be (receiver should know what to do with all those variables). So this makes me think .mem saving is more generic. ADO is interesting you can save and restore a whole table or hierarchic XML (but not easy always).
Sometimes I even pack few cursors to an object and pass it between sessions along with other properties serving as parameters. I didn't yet try saving such an object to a .mem file. If it works probably would be my choice for the job.
Cetin