Accessing Navision DB from Perl via ODBC

waverly
Member Posts: 4
Okay, here's my problem. I'm currently running a Navision 2.01b database on an NT 4.0 server and the 2.01b client on a W2k box. I have the Navision ODBC driver installed on the w2k box and I'm using the Perl ODBC module to access the Navision database. My problem with this, is that whenever I query the database (i.e. "SELECT * FROM Item"), I get nothing returned.
Just for kicks, I decided to try and open the NF DB through Access, and it worked fine. I could view all of the Navison tables through Access. Again, for kicks, I decided to setup the Access ODBC driver, and connected to the Access Database that I had just linked tables into from Navision, from Perl. When I queried that DB, it worked fine. Why is it, that I can query an access Database which is linked to the NF DB, but I can't query the NF DB directly? This has perplexed me for the past month and a half. Can anyone help?
Just for kicks, I decided to try and open the NF DB through Access, and it worked fine. I could view all of the Navison tables through Access. Again, for kicks, I decided to setup the Access ODBC driver, and connected to the Access Database that I had just linked tables into from Navision, from Perl. When I queried that DB, it worked fine. Why is it, that I can query an access Database which is linked to the NF DB, but I can't query the NF DB directly? This has perplexed me for the past month and a half. Can anyone help?
0
Comments
-
Sorry I can't you with your question, but as someone similarily perplexed with ODBC and SQL maybe you can help me!
I need to select and update dBaseIV files from Navision, I am using an ocx to run SQL commands, but I need to sort out the DSN.
I am attempting to configure a datasource using a Microsoft ODBC driver. From ODBC dBase setup I select directory, no problem, I then select Indexes and I can see a list of the .mdx files, but there is nothing in the 'List Files of type' list and no indexes are listed in the 'Select Unique Record Identifier' window for the .mdx file.
It just doesn't seem to work under Windows 98, but on a p.c. running Windows NT it is showing the unique identifiers!
Any ideas anyone? It's driving me crazy!0 -
Sorry, I don't know anything about dBaseIV or OCX. Y'know, I didn't really think about it, but could it be possible that Windows 2000/NT and 98 react differently with the ODBC drivers? Could explain a lot of problems I've been having.0
-
I've just been on a tour of our office conducting an experiment on which ODBC driver works on which windows version, with inconsistent results. (i.e. allows you to select unique record identifiers from the select indexes window when setting up the DSN.) However, I did find that driver ver. 4.00.4403.02 with core components ver. 3.520.4403.2 works on NT but does not work on a windows 98, so I guess this proves you are probably right!
As for all the other versions:
driver 3.50.3428.00, core comp. 3.510.3711.0 works on win 95
As for wnodows 98, nothing seems to work.
Fascinating eh?!
Does anybody know whats going on here, because this problem is coming between me and a nifty interface.0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions