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 on 64 bit - not the usual numpty error!
MaxBatSWRI
Member Posts: 2
Hi All,
We usually get through our trials and tribulations with Dyanics Nav. o.k. We're stll on 5.0 but it works well for us and we do some good things with it.
However, we (three of us plus users) are stumped in this one. Every avenue has been tried but we cannot get one of our VB programs to run on 32 or 64 bit Vista or Win7 when it has been published from a 64 bit machine. It does run on 32 and 64 bit machines when published froma a 32 bit machine. This applies whether we use VB 2008 or 2010 expresses.
Any ideas? Are doing something basic wrongly?
We can access our Dynamics databases programatically using the Syswow64 ODBC32.exe from Excel 2010 (32 bit) on 64 bit machines, no problem. The message we get from vb reports that there is no DSN - msg is System.Data.Odbc.Odbc. Exception ........ ERROR[IM002] ....... Data source name not found and no default driver specified.
Odbc32 in control panel shows an unconfigurable User DSN but no System DSN. SYsWoW64 shows a fully functioning System DSN which is named to match the call in the VB program.
Any ideas? Pretty sure it's not ODBC but am concerned about the absence of the unconfigurable System DSN in standard (non SysWoW) odbc32.exe
Cheers and thanks for your attention.
Max.
We usually get through our trials and tribulations with Dyanics Nav. o.k. We're stll on 5.0 but it works well for us and we do some good things with it.
However, we (three of us plus users) are stumped in this one. Every avenue has been tried but we cannot get one of our VB programs to run on 32 or 64 bit Vista or Win7 when it has been published from a 64 bit machine. It does run on 32 and 64 bit machines when published froma a 32 bit machine. This applies whether we use VB 2008 or 2010 expresses.
Any ideas? Are doing something basic wrongly?
We can access our Dynamics databases programatically using the Syswow64 ODBC32.exe from Excel 2010 (32 bit) on 64 bit machines, no problem. The message we get from vb reports that there is no DSN - msg is System.Data.Odbc.Odbc. Exception ........ ERROR[IM002] ....... Data source name not found and no default driver specified.
Odbc32 in control panel shows an unconfigurable User DSN but no System DSN. SYsWoW64 shows a fully functioning System DSN which is named to match the call in the VB program.
Any ideas? Pretty sure it's not ODBC but am concerned about the absence of the unconfigurable System DSN in standard (non SysWoW) odbc32.exe
Cheers and thanks for your attention.
Max.
0