Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 295 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
ODBC to NAV 2009
daves
Member Posts: 49
We are in the process of upgrading a database to NAV 2009, native database (SQL Server later). UPS Worldship accesses the database via NODBC. We are getting the error shown below when we attempt to have Worldship read data from NAV.
Dave
We have tested using Excel to access the database - no problem. It is obvious from the behavior of UPS Worldship that it is able to open the database and map to the desired table (a clone of the customized Sales Header table). The error occurs when UPS Worldship attempts to read from a table containing shipment info. The application works fine with the V4.0 ODBC connector but not the NAV 2009 ODBC connector.
The error message is somewhat garbled, but it consistently comes out that way. The test NAV 2009 dtabase server is running on a Windows 2008 Server system. Naturally UPS says it's a Microsoft problem, not a UPS software problem.
Any ideas as to the cause / possible solutions?
Thanks,
Dave
We have tested using Excel to access the database - no problem. It is obvious from the behavior of UPS Worldship that it is able to open the database and map to the desired table (a clone of the customized Sales Header table). The error occurs when UPS Worldship attempts to read from a table containing shipment info. The application works fine with the V4.0 ODBC connector but not the NAV 2009 ODBC connector.
The error message is somewhat garbled, but it consistently comes out that way. The test NAV 2009 dtabase server is running on a Windows 2008 Server system. Naturally UPS says it's a Microsoft problem, not a UPS software problem.
Any ideas as to the cause / possible solutions?
Thanks,
Dave Studebaker
Co-Founder Liberty Grove Software
Author: Programming Microsoft Dynamics NAV (V5.0), 2009, 2013
Co-Founder Liberty Grove Software
Author: Programming Microsoft Dynamics NAV (V5.0), 2009, 2013
0