Re: access 2003
- From: "Geoff" <geoff@xxxxxxxxxx>
- Date: Sun, 6 Aug 2006 15:39:18 +0100
Since Microsoft did not instruct me to remove the
Me.FilterOn = False, Me.Requery I was puzzled and could not
understand the need for this portion and wondering if I had missed
something. In short, I believed more was to yet to be revealed as a
result of discovery or further explaination with regard to upgrade or
corrections from Acess 97 to Access 2000 or Access 2003.
I expected a patch from Microsoft to solve this problem. Your
synopsis of the filters actions and goals confirmed my thought process.
I think your expectation is spot on - that a patch will, eventually, be the
order of the day. (But we'll have to wait and see.)
As you know, I'm getting the same behaviour in Access 2002. Therefore, it
seems Microsoft have inadvertently introduced a product change sometime
after Access 97 and before Access 2002. It must be inadvertent because the
Access 2002 online help system continues to assert (as expected) that:
"You can remove a filter by ... using Visual Basic to set the FilterOn
property to False."
If this is a general issue, then I guess Microsoft will need to consider
what customer advice or patches they need to provide and for what products.
Very, very interesting. Well done. Please keep the newsgroup posted.
Regards
Geoff
.
- References:
- Re: access 2003
- From: Geoff
- Re: access 2003
- From: Geoff
- Re: access 2003
- From: Geoff
- Re: access 2003
- From: doglover
- Re: access 2003
- Prev by Date: Re: access 2003
- Next by Date: Re: MS Upsizing Wizard Wont Transfer Data
- Previous by thread: Re: access 2003
- Next by thread: Database opens as Read Only in Access 2003
- Index(es):
Relevant Pages
|