There is an issue with the original Crystal Reports 9 when verifying the database in a report that uses the DBISAM ODBC driver. The following error message appears:

"The database table <TableName> cannot be found. Proceed to remove this table from the report?"

Crystal has issued a hot fix to resolve this problem and you can download it from this link:

ftp://ftp.crystaldecisions.com/outgoing/ehf/cr90dbexwin_en.zip

In their ReadMe PDF file included with the hot fix they describe the problem incorrectly, but the fix does resolve the problem. They indicate that the fact that the DBISAM ODBC Driver doesn't support catalogs is the source of the problem, however this is not the case. The DBISAM ODBC Driver does indeed support catalogs, rather the problem is that Crystal Reports 9 was parsing catalog names that are also directory names, such as is the case with local catalog names, and treating everything after the first backslash as a schema name even though the DBISAM ODBC Driver specifically reports that it does not support schema names. Previously with Crystal Reports 8.5, these types of catalog names were kept intact, as they should be because that is what the DBISAM ODBC Driver indicates is the catalog name.