Bill Benson
bensonforums at gmail.com
Sat Dec 27 14:59:34 CST 2014
I have used filters sometimes in the past, and the way they interact with filteron, their picky syntax, the inability to set and forget them, because they are not dynamic like a controlsource; they are easy to be made obsolete. And I usually can't recall whether recordsetclone is or is not affected by the filter when filteron is true, I have to keep looking that up! I give them the well earned label of "tricky"; I also wish there were a filters collection for increments and decremental filters. On Dec 27, 2014 12:03 PM, "Gustav Brock" <gustav at cactus.dk> wrote: > Hi Bill > > No, filters are not very tricky. But the filter can only be changed if > something tells it so. > So either you will have to use the AfterUpdate event of the other form to > reapply the filter, or you can use the OnActivate event of the form to > check if the value to filter for has changed on the other form. > > /gustav > > ________________________________________ > Fra: accessd-bounces at databaseadvisors.com < > accessd-bounces at databaseadvisors.com> på vegne af Mark Simms < > marksimms at verizon.net> > Sendt: 27. december 2014 17:22 > Til: 'Access Developers discussion and problem solving' > Emne: Re: [AccessD] trying to filter a form on a control's value > > Yes, that toggle is required. Filters are very tricky. > > > > > Are you setting the Filter On property too? I seem to recall needing to > > set filter on to False, setting the filter, and then setting filter on > to True. > > > > Charlotte > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >