The preceding topics demonstrated how easy it is to create data source components — first as an ActiveX control, then as an ActiveX DLL. Those aren't the only options either. You could just as easily create an ActiveX EXE data source, or simply use a data-aware class as a data source. So how do you decide? There aren't any hard and fast rules, but here are a few suggestions:
In addition to choosing the type of data source, you also have a lot of flexibility when it comes to choosing a data interface. As demonstrated in the preceding topics, you can easily switch between OLE DB and ODBC data source using just about any database as a back-end.
Perhaps the most intriguing option is the OLE DB Simple Provider. The example demonstrated the use of a simple text file as a data source, but that's just the tip of the iceberg. With OSP, you have complete control over how and where the data is stored. You can create your own custom file formats, storing data in a binary format that only your component can read. You could even use an OSP component to store and retrieve objects.
With all the possibilities, one thing is certain — data source components elevate data binding to a whole new level.
This topic is the final topic in a series that walks you through creating sample ActiveX data sources.
To | See |
Start from the beginning | Creating Data Sources |