>>Hi,
>>
>>I am testing how I could implement CA as a public object (or referenced by application object) such that it can be used over and over for different SQL commands. For example, when creating reports I need to send to DB a SQL Select and get back the cursor for the report. So my idea is to use the same CA object for all reports.
>>
>>Here is what I tried:
>>
>>1. Created CA (DataSourceType'ADO'), set all the necessary ADODB properties. Then I call CursorFill() and get the cursor for the report.
>>2. Then I close the cursor (use in ("mycursorname"))
>>
>>To get cursor for another report I do the following
>>1. Set new value of alias for the existing CursorAdapter
>>2. Set new value of SelectCmd for the existing CursorAdapter
>>3. Call CursorFill().
>>I get another cursor with no problem.
>>
>>My question is, do you see any potential problems with this approach?
>>
>>TIA.
>
>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.