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 - Multiple Companies Issue
asnape
Member Posts: 4
If you open an ODBC connection to a particular Navision company and then close that connection and try open one to a different company, the second connection is refused, even if all the handles are closed and the connection objects destroyed. If you then quit the application/vbscript and try the connection to the second company again, it then works, but the original connection then fails. Basically you seem to only be able to open an ODBC connection to a single Navision company during the lifetime of any given application.
We’re using C/ODBC version 3.70.01.16172 and the problem happens consistently no matter how we access Navision. I’ve seen it from:
1. vbscript connections
2. SQL DTS packages
3. Third party query tools such as dbQwikEdit Pro 3
I suspect it can also be reproduced from MS Excel or MS Query, but I haven’t tried.
It also happens on multiple machines, including the Navision servers itself.
Any Ideas why?
We’re using C/ODBC version 3.70.01.16172 and the problem happens consistently no matter how we access Navision. I’ve seen it from:
1. vbscript connections
2. SQL DTS packages
3. Third party query tools such as dbQwikEdit Pro 3
I suspect it can also be reproduced from MS Excel or MS Query, but I haven’t tried.
It also happens on multiple machines, including the Navision servers itself.
Any Ideas why?
0