>>>Hi,
>>>
>>>I am using arrays as way to pass the information from UI to BIZ/DA objects but thinking about changing to objects (using SCATTER/GATHER). In terms of memory use, do objects require more memory?
>>
>>Why not try it the ".NET" way?
>>
>>CursorToXML() and XMLToCursor() can blast a cursor or table to a file or memvar (i.e. string) and back again in no time; e.g.
>>
>>

>>m.foo = ""
>>use MyDbf
>>CursorToXML("MyDbf", "m.foo", 3)
>>XMLToCursor(m.foo, "BOPlenty")
>>browse
>>

>>
>>Note the use of "output format option 3" (attribute centric XML) which uses around 40% less markup than element centric.
>
>The format option 3 has done the following:
>- an integer column containing zeros was interpreted as a logical containing .f.; when I put a two digit number into one of the last rows, it came across as n(2), again not integer. I guess if it had all zeros and then greater and greater numbers approaching the end, Fox would have some work to do adjusting the widths, column type etc.
>- datetime columns came across as c(1) (all fields blank). Then when it wasn't empty, it came as c(19) containing ttoc(value, 3).
>
>IOW, nice if all your data are strings.

Hi Dragan,

I observe the same (odd) phenomenon with Cursor2XML even without parameter 3. That is, some fields change the type in the conversion. Thanks for catching this issue.