ADO Recordset interface?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Craig Buchanan - 28 Sep 2005 13:50 GMT

I'd like to make a class that would appear to be an recorset for the purpose
of binding it to a Access form, yet still be able to create custom
properties and methods. Is there an interface exposed by ADO that would
allow me to do this?

Thanks,

Craig Buchanan

Reply to this Message

rkc - 29 Sep 2005 01:18 GMT

> I'd like to make a class that would appear to be an recorset for the purpose
> of binding it to a Access form, yet still be able to create custom
> properties and methods. Is there an interface exposed by ADO that would
> allow me to do this?

Custom properties and methods for the purpose of doing what?

You can create a class that has a recordset as a member and then
create methods in the class that act on that recordset.

Reply to this Message

Craig Buchanan - 29 Sep 2005 21:44 GMT

thanks for the response. I would like to insulate the client layer from
direct interaction with ADO objects. I would like my application's API to
only expose 'business' classes.

> > I'd like to make a class that would appear to be an recorset for the purpose
> > of binding it to a Access form, yet still be able to create custom
[quoted text clipped - 5 lines]
> You can create a class that has a recordset as a member and then
> create methods in the class that act on that recordset.

Reply to this Message

rkc - 29 Sep 2005 22:25 GMT

> thanks for the response. I would like to insulate the client layer from
> direct interaction with ADO objects. I would like my application's API to
> only expose 'business' classes.

Well a bound form is going to have direct interaction with a
recordsource of some type. There's no getting around that.
That doesn't mean you have to write all your code in the
form class modules. You can create a class that handles the
creation of an ado.recordset based on the needs of your business
classes. The recordset object can be exposed as a property of that
class which can then be used to set the recordset of a form.

>>>I'd like to make a class that would appear to be an recorset for the
>
[quoted text clipped - 8 lines]
>>You can create a class that has a recordset as a member and then
>>create methods in the class that act on that recordset.

Reply to this Message

Craig Buchanan - 30 Sep 2005 16:09 GMT

my thought was that if i build a class that implements the recordset object,
then i could bind the form to the class directly, yet still mantain my
encapsulation. the code won't allow an object to implement an
ADODB.Recordset, but maybe a lower-level interface is available.

> > thanks for the response. I would like to insulate the client layer from
> > direct interaction with ADO objects. I would like my application's API to
[quoted text clipped - 20 lines]
> >>You can create a class that has a recordset as a member and then
> >>create methods in the class that act on that recordset.

Reply to this Message