tags:

views:

24

answers:

0

While worked in Windows, I developed a ODBC driver for a database, I installed and registed it in system, and created a data-source(I'am sure about this,because I can see these utils in system's datasource manager), while I call SQLConnect() use the data-source name, the IM003 throwed and the native error is 160, it means that the SQLConnect()'s calling can't find the driver and the loading failed.

I check the driver directory and ther ODBC-API calling, they worked well. I know, until I call SQLConnect(), all the SQLAllocHandle()'s calling are system calling, not my ODBC driver's, the question is, how should I debug the error? Is anything lack or 'must-adding' in my ODBC driver encapsulation?