>>Typically - in my VFP9 application - business classes are instantiated in the LOAD of the form. I usually drop the class object on the form - at design time - and the class is instantiated automatically in the LOAD of the form.
>>
>>Now I need to instantiate an object of a class in code (in a PRG file). So far, the only way I found I could do it is as follows:
>>
>Not enough detail WHY you need to do it in code, as this might decide your decision.
>If the ONLY reason is that during the runtime the class gets identified,
>.AddObject() on the form or a subclass is better as object cleanup is handled via garbage collection.
>
>If you have to exchange this object, the .addproperty() is similar to createobject() or newobject()
>insofar as cleanup is concerned.
>
>HTH
>thomas
Actually I found that I do not need to instantiate the class. I simply need to select the table in the cursor. Then, check values in a row and column of the cursor. Much simpler than instantiating the class.
All set.
"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