Why Filter do not function?

Belias
Belias Member Posts: 2,998
edited 2007-08-03 in Navision Attain
I noted that filters like <>A* does not function in navision. the '*' character is read as it is and not for a part of string (as in filters like A* is done). in Nav 4.0 there isn' this problem.

is there a work around about that?
-Mirko-
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog

Comments

  • Waldo
    Waldo Member Posts: 3,412
    Not really true.
    I tested in 4.0, and a filter <>T* gave me records starting with "T" as well.

    As a workaround you could be filtering in code ... using temp tables ... . Only thing about that is that it would only be for that one field that you program it for ... :| .

    Sorry ...

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • Belias
    Belias Member Posts: 2,998
    i had already tried to filter using code, but it doesn't work.(in nav4.0 the filter works!)
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • kine
    kine Member Posts: 12,562
    1) I posted somewhere about this problem before, but who will find it in the heap... :-)

    2) From On-Line help about entering filter criteria:
    <>
    Not equal to
    <>0
    All numbers except 0

    The SQL Server Option allows you to combine this symbol with a wild card expression. For example, <>A* meaning not equal to any texts that start with A.

    It means, this is working just on MS SQL server and not in native DB.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.

Categories