What interface to implement to be a datasource to VB data bound control?
-
I have created a COM collection object for use by our UI team, but now requirements seem to have changed and they no longer want COM collections but something like ADO recordsets they can bind to their grids. It seemed to me that a data bound control is probably just using an interface on the ADO recordset objects to navigate the collection. And since I already had my COM collection implemented, if I could implement this mysterious DataSource interface I could make everyone happy. Can anyone give me a push in the right direction? What interface do I need to implement in my COM collection to act as a DataSource for a VB Data Bound control? Thanks in advance.
-
I have created a COM collection object for use by our UI team, but now requirements seem to have changed and they no longer want COM collections but something like ADO recordsets they can bind to their grids. It seemed to me that a data bound control is probably just using an interface on the ADO recordset objects to navigate the collection. And since I already had my COM collection implemented, if I could implement this mysterious DataSource interface I could make everyone happy. Can anyone give me a push in the right direction? What interface do I need to implement in my COM collection to act as a DataSource for a VB Data Bound control? Thanks in advance.
Take a look at the ATL OLEDB data producer classes1. Many grids support OLEDB as well if I'm not mistaken.. Just fire up an ATL project, and add an OLEDB data producer class using the ATL wizard, and go on from there. :) 1 I'm not sure this is the correct name. I'm 100 miles from home, so I can't lookup the name right now. But just look at the ATL wizards and you'll know it when you see it. -- Only in a world this shitty could you even try to say these were innocent people and keep a straight face.