It has to do with the way Crystal Reports interprets boolean values. Check the datatype of the field your working with. I never saw this with 4.5,5, or 6. I first encountered this same error converting5.0 reports to 8.0. I believe it has to do with the way crystal (or more likely ODBC) handles boolean data types. Since there are so many different variants depending on your dbms, this sort of jacks up crystal. In the old days you could evaluate a boolean as either a number OR a boolean. Now it's a little stricter, there's a difference between {Incident.OSHARec} = TRUE and {Incident.OSHARec} = 1 (obviously asuming {Incident.OSHARec} is boolean). I was really hoping this would be fixed in 9.5, but no...