SETFILTER in SQL Database different with Native Database?
intelcore2quad88
Member Posts: 7
Hello everyone,
I have the issues below: When i release my report to Customer, they say that number in report is wrong, but when I backup database and restore to my laptop, I have the right number! After that, I know my customer run NAV with Native Database, I run with SQL Database, and I have the problem with SETFILTER command:
- In Native Database, it return Data with G/L Account No: 13199

- In SQL Database, it does not return Data with G/L Account No: 13199

So, this is reason why Customer run report which return wrong number, but I run report return right number #-o
Has everyone had the problem yet?
Thanks.
I have the issues below: When i release my report to Customer, they say that number in report is wrong, but when I backup database and restore to my laptop, I have the right number! After that, I know my customer run NAV with Native Database, I run with SQL Database, and I have the problem with SETFILTER command:
GLEntry.SETFILTER("G/L Account No.",'<>131*');
- In Native Database, it return Data with G/L Account No: 13199

- In SQL Database, it does not return Data with G/L Account No: 13199

So, this is reason why Customer run report which return wrong number, but I run report return right number #-o
Has everyone had the problem yet?
Thanks.
0
Comments
-
Check whether these posts are helpfull or not
http://www.mibuso.com/forum/viewtopic.php?t=18962
http://www.mibuso.com/forum/viewtopic.php?t=232190 -
intelcore2quad88 wrote:I have the issues below: When i release my report to Customer, they say that number in report is wrong, but when I backup database and restore to my laptop, I have the right number! After that, I know my customer run NAV with Native Database, I run with SQL Database, and I have the problem with SETFILTER command:
WRONG. Your issue is that you are developing in a different environment to that which your customer is using.
You must use the same versions for development and testing and live.
This is just one of many things that are different between the two databases.David Singleton0 -
As David suggested there is difference between the sorting of "Code" field in Native and SQL db.CA Sandeep Singla
http://ssdynamics.co.in0 -
After I have tried some expression filter, I decide not to use : <>A*, because no expressions return right value in Native Database!
So I decide to choose another way.
This is my way:Before 1. GLE.SETFILTER("G/L Account No.",'<>A*&<>B*'); 2. GLE.SETFILTER("G/L Account No.",'%1&%2','<>A*','<>B*'); 2. GLE.SETFILTER("G/L Account No.",'<>%1&<>%2','A*','B*'); => all are fail After Create new variable GLE2 1. GLE2.SETFILTER("G/L Account No.",'A*|B*'); //Get entry contain "G/L Account No." = A* or B* 2. IF GLE.FINDSET THEN REPEAT IF NOT GLE2.GET(GLE."Entry No.") THEN BEGIN ...........//Doing with entry no contain "G/L Account No." = A* or B* END; UNTIL GLE.NEXT = 0; => return right value
Thanks for everyone.
0 -
SETFILTER("...",'<>XYZ*'); does work on SQL but on native it doesn't work.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!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
- 322 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

