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
Different Filter behaviour Table Filter (Form) and Table
victor73
Member Posts: 55
Hello Fellows,
another strange behaviour, can someone explain why the following is happening?
If I use the table filter on a form and apply for example *TÓTH* i get correctly a record on the form and if I apply * TOTH* (without that special char "Ó") I don't get any record and that's the correct behaviour!
But if i do the exact same two operations directly on the table (from object designer) in both cases i receive records---> that's not absolutely correct!
This is important because the direct consequence is when by code I use setfiler(Table.field,*TOTH*)-> I receive a record---> not correct, I shoudn't. I should get a record only in case I do the following setfiler(Table.field,*TÓTH*)
Can someone tell me what causes this starnge behaviour
Thanks a lot
another strange behaviour, can someone explain why the following is happening?
If I use the table filter on a form and apply for example *TÓTH* i get correctly a record on the form and if I apply * TOTH* (without that special char "Ó") I don't get any record and that's the correct behaviour!
But if i do the exact same two operations directly on the table (from object designer) in both cases i receive records---> that's not absolutely correct!
This is important because the direct consequence is when by code I use setfiler(Table.field,*TOTH*)-> I receive a record---> not correct, I shoudn't. I should get a record only in case I do the following setfiler(Table.field,*TÓTH*)
Can someone tell me what causes this starnge behaviour
Thanks a lot
0
Comments
Otherwise check the filter you set by code from the UI. Is it the correct one? If not, try to find out the numeric character value that NAV uses for that character in the database and use that to specify the filter. NAV does some strange things with character encodings in the C/AL editor and in objects exported as text.
First of all, I don't think temporary tables have nothing to do with the issue, because as I said in my first topic I am having the issue directly on running the table in object designer so temporary tables are not causing the strange behaviour!
Then concerning the other suggestions, they'd be valid if the strange behaviour was given only on the C/AL environment, but it occurs filtering when running the table. So we have to resolve the problem there!
Any other suggestions out there??
Thanks to all you folks
With an SQL Server Database, the database collation (in NAV the setting on the Collation page of the Database New/Alter form) influences the searching and sorting (and therefore filtering) within the database. For temporary tables a scheme much like the native database was used. So, yes, it matters.
And since the filtering on the real table does not perform to your liking, you need to change the database collation. Make sure, Accent-sensitive has a tick (in NAV) or your SQL collation contains the string _AS
Apart from that, I am at a loss...
I resolved it changing database collation and making sure that Accent-sensitive has a tick
Thanks for your great suggestion
:P