We have the same error in some of our databases. So far we have not exactly found out how to solve it, but one of our external consultants are working on it, so we hope… Our situation has been similar. But then again not. We upgraded from 2.60 to a 3.01 SQL database. My own guess to what was wrong is that while upgrading the collation was changed. The database is using Simplyfied Chinese, where no lower/uppercase exists. The error only occurs in CODE fields and just looking at it show us that’s wrong. When our consultant is done working on it, I will be happy to report more…