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
Is NODBC driver capable of returning floating points?
![[Deleted User]](https://w4.vanillicon.com/47f7909ff5d96e83d9bf6e9efa4631c3_100.png)
[Deleted User]
SchagenPosts: 0
At my workplace we have the following setup:
Navision 2009 with a native database.
We query this database from a VB6 application (only Select queries).
We use NODBC driver: "Microsoft Dynamics NAV Driver – 6.00.32012.00 NODBC.DLL 11-12-2010", via an ODBC system DSN.
We recently upgraded from Navision 3.7, where we used CODBC for connection to the (also native) database.
The connection from VB6 to the Nav2009 database works fine, but I have one question. This regards the handling of floating point numbers, that is, variables of type double in VB6.
In the old code as it was written for Nav 3.7 / CODBC it looks it was necessary to check for an accidental interchange between decimal separator and thousands separator. This was done by a simple check, something like: if number > 99999 then number = number / 100000. So it looks like that in the old code floating point numbers were transported as a text string. And as a consequence of that our VB6 code had to convert that to a double.
Unfortunately I can not test this any more because the Nav 3.7 database was already removed.
After we started using the NODBC driver, I am under the impression that the driver is capable of returning floating point numbers (doubles in VB6). If that is correct, that would mean that I can remove the comparison to >= 99999.
Can anybody shed some light on this?
Regards, Rudolf Stammis
Software engineer
Navision 2009 with a native database.
We query this database from a VB6 application (only Select queries).
We use NODBC driver: "Microsoft Dynamics NAV Driver – 6.00.32012.00 NODBC.DLL 11-12-2010", via an ODBC system DSN.
We recently upgraded from Navision 3.7, where we used CODBC for connection to the (also native) database.
The connection from VB6 to the Nav2009 database works fine, but I have one question. This regards the handling of floating point numbers, that is, variables of type double in VB6.
In the old code as it was written for Nav 3.7 / CODBC it looks it was necessary to check for an accidental interchange between decimal separator and thousands separator. This was done by a simple check, something like: if number > 99999 then number = number / 100000. So it looks like that in the old code floating point numbers were transported as a text string. And as a consequence of that our VB6 code had to convert that to a double.
Unfortunately I can not test this any more because the Nav 3.7 database was already removed.
After we started using the NODBC driver, I am under the impression that the driver is capable of returning floating point numbers (doubles in VB6). If that is correct, that would mean that I can remove the comparison to >= 99999.
Can anybody shed some light on this?
Regards, Rudolf Stammis
Software engineer
0