The use of <> whilst setting up a definition query

[PatrickMurphy1]

Over the last couple of years I've been using the <> in query builder to exclude out certain categories, unfortunately this year it doesn't seem to be working anymore.

I am using the same data, the same version of ArcMap (10.0 Service Pack 5).

Would be any obvious reason for this

Paddy 

[DanPatterson_Retired]

Not sure.... often != is used to represent not equal to

[PatrickMurphy1]

Hi Dan

I tried that and it didn't work, when i verify its telling me "The expression was successfully verified"

Thanks anyway

Paddy

[PatrickMurphy1]

Hi Sol

The data is from an SDE server. It is a String field, Unfortunately I don't have access to the SQL databse.

Cheers

Paddy

[PatrickMurphy1]

Hi again Sol,

I tried that and the same result, All records were selected

Paddy

[PatrickMurphy1]

=, came up with an error when I verified it.

I'm using the options from "Get unique Values" so case sensitivity doesn't apply.

It might be a matter of doing the Query the long way

Thanks

Paddy

[PatrickMurphy1]

This is how my query is set up, the intention of this is to show all categories except "Complete" and "Expired"

Also this is the Error I received when using the =,

[RyanStovern__GISP]

Change your "Or" to an "And" and see what happens. This should give what you want. By using "And" you are telling the query you want all attributes that are not Complete or Expired.By saying "Or" it is confused on which ones to exclude.

[ScottDean]

Make sure it is setup like the following.

[field name]  + operator + value and [field name]  + operator + value

Example

STATUS <> 'COMPLETED' AND STATUS <> 'EXPIRED'

Obviously I do not know what your field is called so that needs to be changed in the example.

[DanPatterson_Retired]

try putting either side of your OR or AND expression in round brackets ie ( )  Also, I assume that you are selecting rather than typing while you build the expression