Ingnore the last response concerning the Blob error. That has more to do with SET ENGINEBEHAVIOR than ComCodeBook. The SQL interpretor for VFP9 does not like the command.

But the comments aobut changing the ComCodeBook code to create another connection string still applies.


>THe error has nothing to do with COMCodebook. It has to do with the configuration string being created or with something in the database that is not supported by the OLEDB provider. Check the stored procs in the db.
>
>>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.
>>