🚀 go-pugleaf

Here is a question for Team B (or others if they can answer)

We have written a COM object which returns _Recordset* (actually it is an
IDispatch** which in the application gets cast to an _Recordset*).  The COM
object is extremely fast in firing sql cals, populating the _recordset and
returning it to the client (that's why we chose to do it that way instead of
just using TADORecordsets, also we couldn't figure out how to return
TADORecordsets from a com object - our com object is also used by other non
builder apps).  In the builder app, for ease of use, we set the Recordset
property of a TADODataSet to our _Recordset*.  This lets us hook a DBGrid up
to it.

So I have a few questions about this:

1) Is this a safe thing to do? (in the destructor of the form that has the
TADODataSet, I've been calling Release() on the recordset property and then
calling Close() on the recordset.

2)  Lookup fields in the DBGrids pose a problem because you need to set
fields as lookup in the TADODataSet in design time, which doesn't work
because all the fields seem to get wiped out when you set the Recordset
property.  Is there any way to fix this?

3) When trying to use a DBListBox, I can't because the Field property of the
Listbox can't be set unless there are fields in the TADODataSet in design
time, and if you just type a name into the DBListBox's Field property it
won't bind at runtime anyhow, like the DBGrid will.  Is there any way to get
around this?

Thanks.