I'm pretty good with crystal but this sounds like could be corruption somewhere else; or problem with odbc drivers..
I guess there's some things you could try:
on a copy of the report, try changing the formatting values.
Also try exporting the report to spreadsheet
and also to delimited file. look at the output by opening file in word; if you rename tab delim to .xls you can also click and open immed in xl.
and finally, when I'm developing xtal reports, I often check the source data files using access since I don't have to grab whole file to get first screen. setup a link to the file: file | get external data | link tables | ODBC as source type
| machine data source, select the driver and add a few of the tables from your database that you need.
Do a quick query in design mode, right click on key links and select right type of join.
then drop a few of the fields you need into the grid below and see if get same problem.
these things might help you narrow down what is happening
also, using something like WinSQL (free for lite vsn) browse the database table defs for source data and see what type of data the fields defined as. Maybe there's some type of data that it returns the ODBC drives sometimes have probs with. I.e. there are usually several types of numeric fields; integer, float. long, short, fat, wide... :)