ODBC driver 4.02 and 4.03 with contrary results

richtsteig
Member Posts: 2
Hi,
some of our users are migrating from windows XP to window7 finally.
Which means, that the ODBC driver 4.03 has to be installed (because the 4.02-Version of the ODBC-Driver won't work with Windows7).
Now I'm in a real mess:
With the OptionFieldType set to "text" a simple statement like:
produces contradictorily results:
4.02 finds
"0" for 'not set' and
"4" for "alle" (which means "all")
whereas 4.03 finds
"1" for 'not set' - which in my opinion is obviously WRONG - and
"4" for "alle" (which means "all" and is the same result as 4.02 produces)
Since we still use both operating systems my applications don't behave correctly on the Windows7 machines.
Obviously some sort of "Null-Value-Support" might be added furthermore:
Comparing the resultsets of:
shows, that the first statement find ALL of the creditors in 4.02 whereas 4.03 fetches 0 records.
the second statement just works contrary
Now my bundle of questions:
Is there any way to make 4.03 behave like 4.02 did?
Is there a changelog describing the differences between 4.02 and 4.03?
and first and foremost:
Is the "1"-result of the 4.03 driver a misbehaviour that is correted in future releases?
(see attached grafic for build numbers and results)
Peter
some of our users are migrating from windows XP to window7 finally.
Which means, that the ODBC driver 4.03 has to be installed (because the 4.02-Version of the ODBC-Driver won't work with Windows7).
Now I'm in a real mess:
With the OptionFieldType set to "text" a simple statement like:
select disctinct length(gesperrt) from Kreditor(requesting the Locked-Flag of a creditor/vendor)
produces contradictorily results:
4.02 finds
"0" for 'not set' and
"4" for "alle" (which means "all")
whereas 4.03 finds
"1" for 'not set' - which in my opinion is obviously WRONG - and
"4" for "alle" (which means "all" and is the same result as 4.02 produces)
Since we still use both operating systems my applications don't behave correctly on the Windows7 machines.
Obviously some sort of "Null-Value-Support" might be added furthermore:
Comparing the resultsets of:
select count(*) from Kreditor where Name_2 = '' select count(*) from Kreditor where Name_2 IS NULL
shows, that the first statement find ALL of the creditors in 4.02 whereas 4.03 fetches 0 records.
the second statement just works contrary
Now my bundle of questions:
Is there any way to make 4.03 behave like 4.02 did?
Is there a changelog describing the differences between 4.02 and 4.03?
and first and foremost:
Is the "1"-result of the 4.03 driver a misbehaviour that is correted in future releases?
(see attached grafic for build numbers and results)
Peter
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