I've got a good one here for you guys. I have a report that pulls data Year To Date, numbers based on Leads adn Sales. The report was pulling numbers for the wrong month in Production due to a formate change in a text field that is converted to a number, and then stripped down into two parts, one for Month, and one for Year.
I have the report working, and it pulls the data when I run it directly in Crystal on the Server.
It also works jut fine if I run it from Cystal on my local Machine.
Now here's where the weirdness comes in. We schedule our reports using Central Management Console through Internet Explorer using Crystal Reports Server. I published the Report to Crystal Reports Server and scheduled it to run and output in an Excel Document. When I open the document after it runs, all of the fields are Zero. No data gets pulled in.
If I set the ouput to Crystal Report and run it, I will open the report and it will also show all zeros for the data values. But when I hit refresh, it will pull in all of the appropriate data.
I have NO idea why it's doing this. The original Production Report pulls data in, but puts it in the wrong place, and the numbers are not correct. The new one will not pull in the data, but if you refresh it as a Crystal Report, it pulls in the data, and it is accurate. The ONLY two things that changed were two formula fields, one for Month and one for Year. And they were simple changes to simply trim for Month, and trim for Year off of a text field that is converted to a number with ToNumber. And like I said, if I run the report locally or directly on the server and output it to Excel or Crystal, the data is all there and accurate.
If this was Lotus Notes, which I SO wish it was, it would be an easy fix. I would just simply call a refresh at some point. Can't do that with crystal, just like you can't debug, which is another grudge in and of itself.

I would appreciate any help I can get. Has anyone else run into this with Crystal? This is Crystal 11.5 by the way.

Yep, I've deleted the old schedule and rescheduled. I've even gone as far to delete the whole blasted thing from the server, and re-publish it, setting everything back up from scratch. This particular report does not use paramaters. And the only Selection it uses is based on date field.

I'm at the point now, where I'm just laughing at it, because there's no reason for it to be doing this.

I've been looking at this some more, and from what I am seeing the reason for the report not picking up data is due to leading zeroes in the Month code that was in the report. I've changed the code, and this should work, but instead, when I schedule the report to run, I get an error message. Here are the details: