>>>Objects - instances of classes are created using CREATEOBJECT, NEWOBJECT, ADDOBJECT, etc.
>>
>>Oh, OK. THOSE objects. Yes, in some code I'm using such to add combo class to a grid, where the grid is repeatedly populated by a dynamic cursor. AND the source of the combo is a table too. That sort of thing? So with each new cursor to populate the grid I should destroy the previous combo?
>>
>Not only that: imagine a goApp "living" in default datasession. If you have common service classes querying lookup tables, you might want to house them there so that they are counted only once in the number of total objects (MUCH MORE important back in vfp6, vfp7 I skipped) instead of aggregating an instances on each running form.
>
>Works wonderful if they return an array for combo's or memory biz objects, but is lousy for returning a cursor into the private datasessions of forms or returning objects like from a table based factory if those objects also need data access they live in default DS as well. And debugging is much more lively if your tables jump out of scope as soon as you are in a service method on your goApp...
>
>HTH
>
>thomas


Thanks Thomas

I'll have to digest this. As it is teh system has been finished for a few years but I'm now producing a user guide. As I try each piece out I'm noticing little "nonkies" that I'm fixing as I go along. SO I'm not really out to rehash the whole project.

Terry