Thanks

More silly questions to follow :)


>I would most likely take this approach:
>
>From David's post:
>
>Others prefer to code CA subclasses more in the style of business objects, with multiple methods added to each that switch around added properties like cSelect, cWhere, cOrder, then dynamically intercept and change the SelectCmd in the BeforeCursorFill method (which persists then for any CursorRefresh calls). This might include methods on a caCustomer subclass like GetListByState, GetByPK, and so forth.
>
>
>
>
>>Ok, that makes sense.
>>
>>Now another question.
>>
>>In the code snippet I posted, there are various properties that would be changed
>>for each run of the class. For example, I might want only the customer name and
>>balance on one call, then on another, the entire customer record, or any combination
>>of fields.
>>
>>Therefore the CursorSchema, SelectCmd, UpdatableFieldList and other properties would
>>have to be set before each call. This also seems like a good use of the various
>>Before methods.
>>
>>Any thoughts towards this end?
>>