Since upgrading to DB/Textworks 4.2, we've been having this problem. For some reason, there are records that we can't find using
certain searches, but we can sometimes find other ways to search that will
bring them up if we know they're still in the database. For example, I
consistently have trouble when I'm doing a commnand search for records
with
"unknown" in the "listprice" field--it will pull up 2 or 3 records, but
when I search a different way (for "not" in the "date received" field), I
see over 30 records that have "unknown" in the "listprice" field. The
other person here who uses DB/Textworks has the same sort of trouble. Is
there anything that can be done about this?

Thanks!

This is not a bug. This may be a damaged textbase. See the Recover Textbase topic in the DB/TextWorks online help. You need to contact your local dealer or product support for further help on this issue.