Access 2007 Multiselect Form Filter (MS Bug?)

I fixed the problem with the "Contains #error" in the contect menu (relinked the table in the backend), and now it says "Contains xyz" and "Does not contain xyz" like it should....

However, now when I try to filter, I get the error: "The expression your entered contains invalid syntax."

This still seems to be a Microsoft Access bug, since I'm not even coding anything, just selecting an item that MS provides.

Any suggestions?

I created an example where right-clicking on the Locations field in the form and selecting a filter option generates an error.  (I'm not able to upload accdb files, so I made the extenstion mdb and it still seems to work in 2007.)

The problem seemed to start after I made the record source my own SQL statement.  If I select the table itself as a record source, it works.

So this is no big deal, but I can imagine if one needs to draw from more than one table that this could be a problem.  

Or is it something I did wrong in the SQL?

The reason for the split view is, we want people to see an overall view of records, and filter it down to a few records, before accessing detailed information on the one record they want to see/edit.   (The leftmost column will be made into a link that brings up a 'detials view' form)

We have several such split views for accessing different categories of infromation.  The bottom half of the split view (the form) will contain dropdown menus for popular filters.  In most cases, we expect people to use these dropdown menus rather than right-clicking on cells to filter their information.
 
Eventually, I figured out how to get these filters to work programmatically -- I can get a dropdown menu to work with the filter command in VB, by putting ".Value" after the MSDB's field name.  

For example when Locations is a MSDB and filterLocation is a dropdown box with a list of all Locations I can use this as a filter:

    Me.Filter = "Locations.Value Like '" + Me.filterLocation.Value + "'"
    Me.FilterOn = True

But trying to filter by right-clicking on the MSDBs cell in the interface generates an error.  So, although I know the reason this happens (can't use MSDBs in a WHERE or HAVING clause), it still appears to be a MS bug to me, since I'm just using a menu system that MS displays.  If the option generates an error, then it should not be there.  Or maybe I'm just unfamiliar with their way of thinking.

Jeff, I didn't even think about modifying the right-click menu.  In our case it's not incredibly important to make everything totally perfect in that sense, but it's definitely good to know it can be done.  Thanks.