-
Okay this client has a security problem they are scared of. The C/ODBC driver can be togled as we know on read only in options. Now this can't be locked. Any bit knowledgeable individual can move this and other options. (Time-out, cache, identifier) Apart of the fact always some wizz kid can wreck...
-
Okay this client has a security problem they are scared of. The C/ODBC driver can be togled as we know on read only in options. Now this can't be locked. Any bit knowledgeable individual can move this and other options. (Time-out, cache, identifier) Apart of the fact always some wizz kid can wreck...
-
The C/ODBC driver CANNOT connect to a SQL Server - it's impossible. It is a driver only for Navision Server, which is why you're getting this error. If you want to use ODBC to access your SQL Server data you have no option but the SQL Server ODBC driver. Regarding the '.' and other special...
-
Hello, i have trouble with ODBC connect. I am working with Navision Financials 2.60 on MS SQL Server 2000. If creating an ODBC connect with C/ODBC system send error message : S0000[Navison Software a/s][navision Financials ODBC Driver]The TCP/IP connection´s 'host' is not answering (TCP/IP error...
-
I find it usually quite convenient to use Excel, Get External Data, for testing a SQL query. Concerning dates, this told me to use WHERE ("Posting Date"={ts '2001-12-31 00:00:00'}) as syntax. Note that you must use the standard SQL notation for dates (yyyy-mm-dd), and add the timepart...
-
I had the same type of issue with C/ODBC Version - 3.01.01.7794 ([Navision Software a/s][Navision Attain ODBC Driver] Invalid Operand for operator: = (#1023)). I spoke with Navision Support and they said this is an issue with MS Access. There was no additional information provided. The problem also...
-
Hi, I am developping an application to access my navision database with the c/odbc. When I try it with the version 2, it works fine, but when I try to do it with the version 3, it doesn't understand my query. here is my query : String request = "SELECT * " + "FROM \"G/L Entry...
-
Hi Tom, thank you for your answer, it´s problem with standard MS SQL Server ODBC driver because were have Slovak version of NF and in user tables have long names of fields. It´s more dot´s in names and standard ODBC driver work not.
-
Hi, Is their a place where I can get the full documentation on this ODBC driver. I discoverd that especially the version 2 is extreeeemly picky and will crash my program. So I want to treat it gently. Marcel
-
Dates in ODBC are a pain but try #2001-12-31# instead of {d....} or even #20011231#. It sometimes depends on the tool you are using to create the query but microsoft likes (always allows) dates surronded by #'s. Paul Baxter