>>>I don't know if this is really bad approach, but I know that we created a separate CA for each form (or each particular operation). The only exception was CASearch where I set SelectCMD on the fly (still same form).
>>>
>>>The rest of my CAs always were pre-defined and with fixed commands.
>>
>>Thank you. I am just trying to make my approach more memory efficient. If I have just one CA for all my reports, it will be easier to manage (IMHO) and hopefully more efficient from the memory efficient.
>
>You can always instantiate more of the same CA, with different aliases, issuing different commands on them etc, if they operate on the same underlying table(s). The cost is minimal - they are the same class. The buffers etc you'd have anyway when you create multiple cursors.
Yes, it makes sense. Thank you.
"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