I may be mistaken on this, but some of these errors typically occur when there is invalid data in one of the fields in your source.  For example, I most frequently get errors when there is an invalid date in a date field that ODBC cannot interpret.  It is generally not easy to find the offending data, particularly in larger files, since you cannot use any reports to find it.  Typically I am using DFDM to find it.

I don't know specifically what code 14 is but I agree with mhainesalt that it probably has something to do with a corrupt database record.

My approach to isolating the damaged record is to run the report using data ranges to narrow it down until you find it.  For example if you have records A-Z in the file:

1.  Select records from A-M.  If you get no error then you know the bad record is somewhere between N and Z otherwise it would be comewhere between A and M.

2.  Assuming you got an error on A-M,  select records from A - G and use the same logic until you isolate the record. 

3.  When you isolate the record, then use data file display and maintenance to try to determine what is wrong with the record.

Typically I have had to do this with database vendor code 9.  That specific one means a corrupted date field in the file.

This will also happen if you have a bad formula in the report. To test open the report in designer and verify database and try to refresh. If there is an error a formula Crystal will show you the bad formula.

Can you tell us more about where this happens. Is this a new report built from scratch, from a "canned" report, from a form?