Thanks! This wasn't a huge deal for me, but I thought I should let you know about it.

Thanks for the report, that indeed doesn't work properly. You were quite close in your hypothesis, although not exactly right - the problem is in SQL 'like' operator, it assigns different meanings to '[', ']', '%' and '_' characters. It will be fixed in the next release, until then you can surround any of these four characters by '[' and ']'. This means that your string would look like '[[]radio[]]'.

Jiri

[b]Situation:[/b]
1) I right-click on the Artist node and select Filter.
2) I check the "Show just artists with songs which" box and click the "Set songs conditions" button.
3) Under the Advanced tab, I set the condition "Artist contains [radio]".
4) I click OK twice to apply the filter

[b]Result: Nothing gets filtered. All artists are still displayed.[/b]

[b]Hypothesis:[/b] Access uses the square brackets [] to denote a database field in its syntax. I suspect that my "[radio]" expression is messing up some query that is being built for the filter. (I've seen similar problems happen with embedded quote marks in other applications.)

I use brackets in my ID3 info for information that I want to include but which is not part of the actual field's value. For example, the name of a radio show is Alien Worlds. I enter Alien Worlds [radio] in my tags so that I can tell that this "artist" is really a radio show and not a musician when I'm looking at the artist node. I was also hoping to filter on it if I wanted the artist node to show ONLY radio shows.