Access 2000 does not recognize my binary file

[glively]

I am using LabWindows 5.5 and the SQL toolkit to store results in an Access 2000 database. I want to be able to store bitmaps as an OLE object. I am using the DBPutColBinary function to stored the file into a record whose data type is defined as an OLE object. When I go into access to look at the file, the field shows as "long binary data', and when I try to open it I get a message from Access that says a problem occured while communicating with the OLE server. I am using the MS Access OBDC driver. When I try to use the CVI SQL 2.0 dbase driver, I get errors on the DBActivateSQL command that says that the request is not supported by this driver. How can I get this to work?

[Jason F.]

I'm not sure about the OLE Server error that you are getting from your Access database since we really don't provide database specific technical support (also because I don't use Access that much), but for your question regarding which database driver you should use, the answer is the Access ODBC driver and not the CVI SQL 2.0 dbase driver.

The CVI SQL Toolkit also comes with several other ODBC 3.5 compliant drivers that you can use (although they are not as fully functional as the ones that come with the databases themselves) but you only have access to them if you install them with the SQL Toolkit and register them appropriately with the ODBC administrator dialog in Windows. Also, if we do not provide an ODBC driver that you wish to use or you are not satisfied wit
h ODBC drivers in general you can also connect to ADO providers with the SQL Toolkit, which Access does support.

It should be noted though that the functionality supported in a database is not universal across all providers and that the CVI SQL Toolkit was designed to work as a general ODBC 3.5 compliant access facility. Errors that are generated by a database may be unavoidable if it requires special considerations that are outside of the scope of ODBC 3.5 and uses special datatypes or query language considerations that are not realistically coverable by a general access library.

Jason F.
Applications Engineer
National Instruments
www.ni.com/ask