Any text field search (in both basic and advanced versions) doesn't include Custom1 field (and probably other Custom fields, but I haven't tested this).
Custom is definitely a text field, at least it is defined in the database as such. I use Custom1 field to keep a lot text information and currently I have to create queries which explicitly address this field. I would like to have it treated as other of those "any text fields" allowing for using basic search.
Beta Testing for Windows Products and plugins
3 posts • Page 1 of 1
Maciek, I've added this to our bug list. We'll get to it in the near future...
fyi, this has been fixed in the MediaMonkey 2.0 release.