Sonny Software

Hello friends, I am puzzled by the behavior of my smart groups. When no records match the criteria of a smart group, the smart group lists the entire contents of the database instead of nothing. Maybe there's a logic to this, but it seems like a bug. If not, is there something I can do in constructing my smart groups that will force it to list nothing if no records match? Thanks, - Sam

If a smart search comes up empty, no references will be shown.

Your search isn't going to do what you think it does. The way it's configured you are doing an indexed search, which ignores punctuation. So your search for "#envy" is really a search for "envy". If you want to include punctuation, you have to change the popup menu from "words begin with" to "characters".

Jon
Sonny Software

hmm, I've changed "words begin with" to "characters" but that still lists my entire database. I should note that as long as there are any matches that meet the criteria, the smart group works as expected. For example, since I use the string #tagged to distinguish between records I have processed into tagged categories and those that have not, as I process the list and add the #tagged tag, the list gets shorter and shorter (once refreshed) until only the last unprocessed item remains. Once I add #tagged to the last item (and no remaining matching records exist) the group switches to showing the entire database. - Sam

Try doing a Rebuild on the library. If you still see this behavior, please compress the library and send it to me at support@sonnysoftware.com.

Jon
Sonny Software

I spent some time on this and have a few more comments about Live Search

1. The # prefix has a special meaning. It tells Bookends what comes next is a unique ID. So you can't use it without quote marks if you want the first character to be a #. If you use quote marks, it's treated just like any other character.

2. There is a bug in the search for certain special characters in the regex search for characters. It doesn't affect searches containing #, but will affect quoted searches for others such as the pipe ( | ), and can result in all references being "found" in error. I don't know if you did any searches involving one of those characters or not. In any case, this will be fixed in the next update.

Jon
Sonny Software

Rebuilding the library fixed the problem. Thanks for your help! - Sam