ODBC error

tvandongen

I am trying to make a connection between an third party application (Clarisoft). Unfortunately the third party application is doing something wrong and the supplier don't know where to look. He asked me if I had sources (and of course we have MIBUSO =D> ) which could give him some clues to find an solution.

Till now we have

- We have set-up a System DSN (using the ODBC setup screens within Windows) to our Micrsoft ERP database;
- We have purchased some third party design software which links to databases using ODBC;
- The third-party software is known to work with other ODBC data sources and we can link to an Excel spreadsheet through ODBC;
- This third party design software can access the list of tables within the database, but cannot access the list of fields within the database;
- The third-party developer has provided the following information:
- The provider is MSDASQL;
- The code is written in Visual C++ v6;
- The database access is carried out using ADO components;
- The _Connection is set-up okay, but when open is called on the _Recordset object, the error number 0x80040E21 is returned.


The exact call is:

_Recordset->Open(vtSource, vtConnection, adOpenKeyset, adLockOptimistic, adCmdText);

Where vtSource is a string containing “SELECT * FROM [Artikel]” and
Where vtConnection is the _Connection wrapped in a Variant;

Can you please let us know:

- Are there any known issues with the ODBC interface in our ERP database?
- Can you suggest why the interface will work in this instance? Are there further configuration settings that need to be made?
- Can you suggest any further tests that would aid debug / solve the problems in this instance?

We are using the Navision ODBC driver 2.60.01.5350 to connect to a NF 260A database.

Thanks for all your help.

kine

C/ODBC drivers have very limited functionality. They are only able to do some basic SQL queries and in older versions there are problems.

I can say only one thing - if you can, do C/SIDE upgrade to some newer version (3.70b, 4.0) and try it there - I think that C/ODBC version 2.60 is not able to work with ADO...