>I would guess you would need to do a bit of a refit to get COMCodeBook to use OLE-DB providers. If it is using SQLConnect() which only works with ODBC, changing the connect string will fail. Also, are you sure the Native data access uses ODBC as opposed to the native data engine?
>
>The easiest refit would probably be to use the CursorAdapter in VFP 8.0 to gather data, this would support Native for VFP data and ADO for OLE-DB providers with the same interface.
>
>BOb

Thanks for the response, but 8.0 is out of the question (as it is not even out yet). It would be nice to know if COMCodeBook even prepared for OLEDB as it has been know for awhile that ODBC is not going to be supported anymore.


>
>
>>It seems that when I executed the wizard to build my test COMCodeBook app, that the VFP database calls defaulted to ODBC connections. The problem with this is that ODBC is no longer supported/maintained my MS and that OLEDB should be the way to access the backend VFP data. OLEDB allows me to execute Stored Procedures in the DB which I need. So I changed the ConnCfg to use VFPOLEDB instead of MSDASQL.1 but I don't think COMCodeBook can handle this change as the COM controls errored in several places. Does anyone know of or have any success in getting the COMCodeBook to use OleDB VFP data source and if so can you share what changes in COMCodeBook need to be done in order to do this.
>>
>>TIA