ArcPro 3.0 Definition Query

[MichaelMcBain]

Is there a definition query bug in ArcPro 3.0?

I'm filtering out certain parking lots by location type or by public access in the same query, but the OR condition isn't removing the correct features. So this query removes zero features:

LOCDESC <> 'Street' OR Access <> 'Private'

While this one removes the ones I want:

LOCDESC <> 'Street' And Access <> 'Private'

[AngelaSchirck]

So, help me understand what you want to filter here.  Are you trying to filter out when either of the two statements are true? e.g. if LOCDESC <> "Street" but Access = "Private"  should be filtered also? 

[RhettZufelt]

Remember, the definition query doesn't 'filter out' features that return true, it shows them and filters everything else.

While this one removes the ones I want:

LOCDESC <> 'Street' And Access <> 'Private'

---

I'd use that one 🙂
R_

[MichaelMcBain]

Since I want parking areas that are not Street or areas that are not "Private" should it be an OR, not and?

I am using the one that gets the job done

[RhettZufelt]

OR will draw all features that are not private, regardless of what the LOCDESC value is, as well as drawing all the features that are not street, regardless of what the Access value is.

R_

[BarryNorthey]

In SQL And and Or are somewhat the reverse of how we use them in English. In English we might say that we want to display (Definition Query) or select (Select By Attributes) only the Pine (P) and Spruce (Sw) stands in this layer (field SP1). IN SQL we would write: SP1 = 'P' Or SP1 = 'Sw' wherein a selection is made when a condition on either side of the Or is met. 

If we wrote SP1 = 'P' And SP1 = 'Sw' (as it sounds in English) no selections can be made because both conditions must be met to make a selection and in this example, a tree can't be both a spruce and a pine .