Well just changing the provider from MSDASQL.1 to VFPOLEDB.1 did not work. I get another OLE Idispatch exception error 1429 indicating that line 1367 "UserDataSource :: OpenConnectionObject() OLE Idispatch exception code 0 from Microsoft OLE DB Provider for Visual FoxPro. Feature is not available.

So my guess is that ComCodeBook, as I have the code, was really set up for ODBC using MSDASQL.1 and developed before VFPOLEDB.1 ever came along. By the way I tested the standalone using MSDASQL.1 and it worked ok against the database.

Since COMCodeBook was free and developed some time ago, my only option is to delve into the classes and see what needs to be changed.


>You absolutely do not need, nor do you want to use both OLE DB and ODBC. Why add that layer of complexity and slow down the application? Change the cProvider to use the VFP OLE DB Provider. MSDASQL is the OLE DB Provider for ODBC. Get rid of it.
>
>
>>I am using the built in ConnCfg table in the DataSource Project. In the table I have the follwoing fields set:
>>
>>cIndex = prm_Connection_Vfp
>>cConnectTo = ""
>>cDataSrc = "C:\MwsData\MasterWebSystem.Dbc"
>>cInitcat = ""
>>cPassword = ""
>>cSecInfo = ""
>>cProvider = "MSDASQL.1"
>>cUserId = "sa"
>>
>>I would assume that I just change the cProvider to "VfpOleDb.1" but I don't think that will quite get it. Do I need both VfpOleDb for VFP9 and an ODBC Driver installed?
>>