microsoft.public.access.forms

This issue did not occur in Access 2000 or earlier: you could not filter a
form using the display value in a combo, only the actual bound value (which
can be hidden of course.)

In Access 2002, MS decided they needed to get the filtering working, so the
user can filter on the display value, even if it is not the value of the
bound column. So, the prefixes started to occur on those tables where the
lookup table itself was needed to match on the display value. It's rather
flakey (i.e. there are some unfixed bugs in Access in this area), but if you
know the name of the lookup table, it's usually fairly consistent.

FWIW, this web page:
http://allenbrowne.com/AppFindAsUTypeCode.html
contains some functions that try to pin down what is the first visible
column of a combo:
FirstVisibleColumn()
what is the mostly likely filter name Access will use for this field:
GetFilterField()
and what name the user knows the control by:
Caption4Control()

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Yarik" wrote in message
news:1193095391.111458.270750@q5g2000prf.googlegroups.com...
> Hello,
>
> In an Access 2003 ADP application, I have a bound continuous form.
> Filtering is enabled.
>
> Usually, when user invokes "Filter by Selection", the corresponding
> filter strings (Me.Filter) contain simple expressions like
>
> ((Manufacturer_Name="Cisco"))
>
> In particular, those expressions usually refer to the underlying
> recordset's columns directly, without using prefixes/qualifiers of any
> kind. So far so good...
>
> I've noticed, though, that in some circumstances, the names of columns
> in the filter expressions get prepended by the form's name. For
> example, like this:
>
> ((fProductProperties.Manufacturer_Name="Cisco"))
>
> where 'fProductProperties' is the name of the form to which the filter
> is app.
>
> The problem is: I can't find any clues on when and why do such
> prefixes appear. What exactly may be causing MS Access to use the
> form's name as qualifiers of column names in filtering expression? It
> looks really bizzarre.
>
> Please help!
>
> Thank you,
> Yarik.