Hi, i have to port data from ms sql server 2000 to Navision Manufacturing 2.01. My plan is to use DTS to do the job, but i get a generic ISAM error on the 1st row on every execution of the DTS. It seems that C/OBC won’t work properly. Can i upgrade to the latest version of C/ODBC, mantaining 2.01 executables? Any other suggestion to avoid these errors? Thanks in advance.
None of the C/ODBC drivers work well with DTS - which uses the OLEDB provider for ODBC. Some get further than others but fall over depending on the data types used. Can’t think of an obvious alternative given that you’re using 2.01.
Ok, it’s a clue… For now, i will bypass c/odbc and create output text and then import that with dataports. [B)] Thanks!
Well, i upgraded the 2.01 database with 3.70 executables, now i’m using this terribile 3.70 c/odbc driver. The point is that i can’t insert data from sql server 2000 to nav 3.70 without getting an ISAM error!!! The mapping of the fields datatypes are oltrageous!!! a navision code 20 become a GUID, a text 30 became a DURATION (???) I’m really depressed…[V][V][V][V][V]
You can read data from sql to navision via oledb automation. Thats very fast
Maybe set up NAS to read from SQL via DAO and do the updating in Navision?
I don’t know about the latest version of C/ODBC driver, but I made C/ODBC version 2.60F work with inserting records from VB. Check here for the problems that I have encountered: http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=3496 Also, search the forum for ‘C/ODBC’ and member name ‘naji’ for ideas that I presented over the years. In particular, you can write ‘OLE-DB to OLE-DB’ or ‘ODBC to ODBC’ transparent pass-through driver that does nothing other than change data types in the fly and insert nulls when needed. I am not sure if this will solve this problem, but it definitely will not solve C/ODBC multithreading problems in a web server for example. There are some source code samples out there, also check ‘OLE DB Simple Provider (OSP) Toolkit’ here: http://msdn.microsoft.com/library/en-us/oledb/htm/oledbpwk_overview.asp?frame=true