Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 305 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
ODBC fails on some tables
Craig
Member Posts: 2
Hi All,
I'm testing with the test database (Company Cronus) in NF 2.01.A via the provided ODBC driver (2.11.00.924). Using both Access 97 and also a program written in Delphi, ODBC fails on the (same) certain tables with "ODBC - call failed" (Access) and "Data provider or other service returned an E_FAIL status" (Delphi). In each case I only get back the column headings, with the rows being either empty or errors. This only happens on a few tables, most are ok. G/L Account fails, but the other GL tables are read ok. I tried some of the hints from this forum (Identifiers etc) without luck.
Any hints would be greatly appreciated.
Thanks in advance,
Craig.
I'm testing with the test database (Company Cronus) in NF 2.01.A via the provided ODBC driver (2.11.00.924). Using both Access 97 and also a program written in Delphi, ODBC fails on the (same) certain tables with "ODBC - call failed" (Access) and "Data provider or other service returned an E_FAIL status" (Delphi). In each case I only get back the column headings, with the rows being either empty or errors. This only happens on a few tables, most are ok. G/L Account fails, but the other GL tables are read ok. I tried some of the hints from this forum (Identifiers etc) without luck.
Any hints would be greatly appreciated.
Thanks in advance,
Craig.
0
Comments
If the tables are linked in access, you sometimes need to delete the link, reboot the machine and then relink them again after the identifiers in the ODBC driver have been changed. Also I have found it important to make sure that the Temporary directory in the advanced option is set correctly.
HTH
Bruce