Yes, I see what you mean.
This will be fixed in the next build.

There is no error message per se - but in MM2.5 when you leave the value field blank and select "does not equal" as the property, it assumes you're searching for tracks that contain some value in the (property) field. In MM3 it gets confused and ignores this search string.

mhendu, could you please write down which SQL errors you get?
i.e. The error message you get.
Thx.

OK, so I wasn't thinking when I wrote my last post. If you select (property) "is unknown" this is the OPPOSITE of selecting (property) "does not equal" and leaving the value field blank. I would like to exclude tracks from my AutoPlaylist that do not have a value in Custom 2. Apparently this is not possible in MM3 - am I mistaken? Would appreciate it if this bug could be fixed. Thanks!

I'm not getting any SQL errors when updating my MM2.5 database with AutoPlaylists into MM3 now, but there is at least one error in the design. Previously in MM2.5 if you had a custom field and wanted to create an AutoPlaylist to exclude tracks that did not have a value in the custom field, for instance, you would select (property) "does not equal" and then leave the value field blank. There is a new condition in MM3 that allows you to say (property) "is unknown," accomplishing the same task in fewer steps, but the AutoPlaylist does not update to this and leaving the value field blank in MM3 does nothing. This is easily fixed by hand after the update but if you didn't notice this and you synchronized a portable device based on a playlist like this you'd end up with a big surprise - my AutoPlaylist ballooned to encompass almost my entire collection after this update.