Accessing Navision from Active Server Page using ODBC

I am trying to access the Navision Database from an Active Server Page using the ODBC driver and am getting the following error message: Error Type: Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Navision Software a/s][Navision Financials ODBC Driver]ISAM error Is there any way to get this to work? Or will I have to dump the information into MS Access then access it? Here is the code I am using to try to access Navision: ’ Establish Database Connection Set conn = Server.CreateObject(“ADODB.Connection”) connStr = “DSN=Navision;UID=USERID;PWD=PASSWORD” Conn.Open connStr Set Session(“myConn”) = conn ’ Open RecordSet strSQLQuery = “select [First Name],[Last Name] from Employee” Set rs = Server.CreateObject(“ADODB.Recordset”) rs.Open strSQLQuery

From what I’ve experienced, you can’t use ADO safely. I don’t believe it’s recommended by Navision US. If I recall, they recommend DAO or RDO. Try those out. Hope that helps you out… Regards, Mark

You can use ASP through ODBC, but like said, keep te security in mind. I wouldn’t try this method for internet, only on an Intranet. Navision does not support record sets like Access does. So you have to use SQL statements. Here is how to open a session to Navision: Set conn = Server.CreateObject(“ADODB.Connection”) DSNString Set Session(“Navision_conn”) = conn Regards, Arjan

Wow, this is exactly what I am experiencing. I used the exact same method as you trying to connect to a Navision database from an ASP page using ADO/ODBC, and got the exact same ISAM error. Have you found a work-around yet? It appears to me to be a faulty Navision 2.5 C/ODBC driver. I can get the thing to work from VB using the ADO Data Control, but it bombs from ASP. I even built an ActiveX DLL that contained the code that worked in VB, registered that DLL on the web server, called it from the web page, and it still bombed. My email address is, so please contact me if you’d like to collaborate on this and see if we can get a solution. But I suspect that the C/ODBC driver is buggy.