If you're doing it programmatically, you've probably missed the "Me.FilterOn
= True" part. Just add that right after Me.Filter, and it should be fine.
I believe whenever you execute that, it automatically requeries, but I don't
have Access handy on this computer, so you'll have to test it yourself and
make sure.
Rob
> Hmmm it does appear the Filters are holding over 255 characters now, it
> must have been one of my string variables cutting them off. However, the
[quoted text clipped - 12 lines]
>>
>> Ryan
aaron.kempf@gmail.com - 21 Oct 2005 19:52 GMT
so in which ORDER should you do this?
what is the best way to apply a filter to make sure that it doesnt do
more requerying than it needs.
I mean.. for starters
IF Me.Filter <> "ROWID = 312" Then Me.Filter = "ROWID = 312"
IF Me.FilterOn <> True then Me.filterOn = True
that would be more efficient. RIGHT?
-aaron
Ryan Langton - 27 Oct 2005 16:30 GMT
Robert,
You're right, I just forgot to set the Me.FilterOn = True.
I went through my code and added that after every Me.Filter = myVar
statement and everything works great now.
Thanks,
Ryan
> If you're doing it programmatically, you've probably missed the
> "Me.FilterOn = True" part. Just add that right after Me.Filter, and it
[quoted text clipped - 20 lines]
>>>
>>> Ryan