# Should PROP:Filter should come before or after the open(MyView)?

**URL:** <https://clarionhub.com/t/should-prop-filter-should-come-before-or-after-the-open-myview/203>\
**Category:** questions\
**Created:** [October 3, 2014, 9:24am UTC](https://clarionhub.com/t/should-prop-filter-should-come-before-or-after-the-open-myview/203 "2014-10-03T09:24:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![brahn](https://clarionhub.com/user_avatar/clarionhub.com/brahn/32/756_2.png) [@brahn](https://clarionhub.com/u/brahn)\
**Post date:** [October 3, 2014, 9:24am UTC](https://clarionhub.com/t/should-prop-filter-should-come-before-or-after-the-open-myview/203/1 "2014-10-03T09:24:47Z")

</div>

Continuing the discussion from [Quick Quiz - View error checking](http://clarionhub.com/t/quick-quiz-view-error-checking/199/2):

> [@Quick Quiz - View error checking](https://clarionhub.com/t/quick-quiz-view-error-checking/199/2):
>
> 1. PROP:Filter should come before the open(MyView)

I did a quick test and it didn’t seem to matter either way. Does anyone have any more thoughts or evidence on the subject?

---

<div class="post-metadata">

**Author:** ![MarkGoldberg](https://clarionhub.com/user_avatar/clarionhub.com/markgoldberg/32/1511_2.png) [@MarkGoldberg](https://clarionhub.com/u/MarkGoldberg)\
**Post date:** [October 3, 2014, 4:31pm UTC](https://clarionhub.com/t/should-prop-filter-should-come-before-or-after-the-open-myview/203/2 "2014-10-03T16:31:13Z")

</div>

see ViewManager.Open in ABFile.CLW

OPEN(SELF.View)  
!..  
SELF.ApplyFilter

---

<div class="post-metadata">

**Author:** ![brahn](https://clarionhub.com/user_avatar/clarionhub.com/brahn/32/756_2.png) [@brahn](https://clarionhub.com/u/brahn)\
**Post date:** [October 3, 2014, 4:45pm UTC](https://clarionhub.com/t/should-prop-filter-should-come-before-or-after-the-open-myview/203/3 "2014-10-03T16:45:49Z")

</div>

Interestingly though it _seems_ to work either way (I have not done any very serious testing). Perhaps because table used by the view is already open?

---

<div class="post-metadata">

**Author:** ![CarlosGtrz](https://clarionhub.com/user_avatar/clarionhub.com/carlosgtrz/32/5870_2.png) [@CarlosGtrz](https://clarionhub.com/u/CarlosGtrz)\
**Post date:** [October 3, 2014, 7:33pm UTC](https://clarionhub.com/t/should-prop-filter-should-come-before-or-after-the-open-myview/203/4 "2014-10-03T19:33:27Z")

</div>

Probably it should be set before the first NEXT(). That’s how it’s documented for PROP:Where

---

<div class="post-metadata">

**Author:** ![brahn](https://clarionhub.com/user_avatar/clarionhub.com/brahn/32/756_2.png) [@brahn](https://clarionhub.com/u/brahn)\
**Post date:** [October 4, 2014, 10:40am UTC](https://clarionhub.com/t/should-prop-filter-should-come-before-or-after-the-open-myview/203/5 "2014-10-04T10:40:00Z")

</div>

Gosh yes, I had not noticed that on the `PROP:Where` although I don’t recall ever using it:

> Note: The SET statement clears any WHERE clause set by the SEND statement.

In the case of `PROP:Filter` though I would think that needs to occur before the `Set` statement. Particularly since `PROP:Filter` can be used for non SQL file drivers whereas the `PROP:Where` is specific to SQL drivers. The example in the help for `PROP:Filter` shows it being applied before the `Open` :

```auto
BRW1::View:Browse{PROP:Filter} = 'Mem:LastName = KeyValue' !Specify filter condition
OPEN(BRW1::View:Browse) !Open the view

```

But as Mark pointed out the ABC Classes do the opposite.