As I am sure you know that VFP allows at least 10 ways to get any job done :)
I got a good input on my question and now ready to move on to the next topic :)
>Your Title points to VARIABLE vs (variable)ARRAY. What you mean is a string PROPERTY vs array PROPERTY. There was something in the thread about PEM, but I've considered this as a possibility only. Then yes, a table would not fit.
>There is also the idea of collection object. This has better dynamic ways to retrieve your data then both property bound solutions. If this is not used high rate I would prefer this.
>
>>You cannot set a cursor to an application class/object (at design time). Only either a string (or other type) property or an array.
>>The question was - see the Title - what is better in terms of memory management, many string properties or an array property. My understanding, since nobody states one way or the other, it is a personal preference.
>>Cursor is not even in the "scope".
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
