I don't see how CD could change the format of a field on the report. The only thing I can think of is if the store number is a parameter and CD is sending it to the report as "1,952.00". This is just a shot in the dark really, but if it's a parameter, try putting a single-quote in front of it in the CD parameter window (eg. '1952 instead of 1952). James

(Just to be clear, I'm not connected to CD in any way. I'm just a user and thought I'd see if I could help) That's pretty weird. I've never seen CD do anything like that. What are you having it do with the report? Print? Export? View? If you're exporting, what format are you exporting to (PDF, Excel, etc.)? Just grasping at straws again, but if you're exporting the report, you could try exporting in a different format. Or, for that matter, if you're not exporting the report, you could try an export (eg. to a PDF file) and see what you get. Maybe Kevin will jump in here with some ideas. James

At this point, my best guess is that it is a bug in the Crystal Reports controls that I use in Crystal Delivery. I don't think I have control over the formatting, but I will need to do some digging to know for sure.

(FWIW, I was going to post this yesterday, but the forum went offline while I was writing my reply.) I'm assuming that you're running CR10 and CD from the same computer. CR uses the default printer drivers to format the report, even when viewing it, so viewing a report on two different computers, with different printer drivers, can produce different results. I don't think it would change the format of a field like that, but I figured there's no harm in checking. I don't use the view option in CD, so there could be a problem there I just haven't seen. If you haven't already, I'd suggest you try printing and/or exporting the report and see if you see the same thing. That might also help Kevin track down the problem. FWIW, all I ever do in CD is export (to PDF files) and I've never seen that problem. James

What's slow? Loading the reports or running them? I assume it's running them. That's presumably a result of the amount of data the report is reading and the available bandwidth of the remote connection. This is not exactly my area, so my initial suggestions are fairly basic. Can you decrease the amount of data being sent to the report? For example, if you're using an SQL stored procedure as your datasource, can it eliminate any unnecessary data (rows or columns), summarize data, etc? Or, can you increase the available bandwidth of the connection, either by increasing the speed or reducing other traffic? Like I said, this is not my area, so there may very well be other things you could try. Getting back to your original problem, did you try exporting a report to see if the crosstab had the same formatting problem? James