Report will not burst

this is interesting - I'm having the exact same thing happen. I created a new bursting structure a few months ago and I've had an employee roster report using that and it has been working just fine for those two months. A couple of weeks ago, I published a new report using the same bursting structure, and it will not burst. I'm having I.T. look into this but so far they haven't come up with an answer. I've deleted and re-added the problem report to see if that solves anything, but it does not. Has anyone else been running into this problem?

Hello Donna, Long time! Try something: check your Record Selection area and if you have anything commented out - delete it. The bursting tags on and still looks at the commented out criteria as if it was not commented out. republish it and test your bursting again. Thanks Anna

Honestly - we have odd issues like this occur occasionally and we will have something just stop working completely and have no reason why. Typically publishing a new version is what "fixes" the issue. However - it seems you have already tried that. I know this may be a silly question - but do you have the bursting data point on your Crystal report? We have had reports not burst and we have had to put the data field on the report itself (not just in the data set). Even if it is a hidden field, it fixed the no bursting issue we had. Not sure that would be your issue but thought I would throw it out there.

Hi - thanks for the feedback. I do have the burst field in the report data. However, I got my report to work by doing something very funky. I took a totally different bursted report that has been running for several years and gutted it - I deleted everything out of it. I then took the sql code out of my problem report and plugged that into the problem report, then I published that and burst it - and - it worked! I have no idea why though. Very strange.

Hi - thanks for the feedback. I do have the burst field in the report data. However, I got my report to work by doing something very funky. I took a totally different bursted report that has been running for several years and gutted it - I deleted everything out of it. I then took the sql code out of my problem report and plugged that into the problem report, then I published that and burst it - and - it worked! I have no idea why though. Very strange.

I'm not sure if this is true, but I was taught to always make sure my bursted fields were groups in my Crystal report. We usually always burst our PO reports by Dist-Co and Acct-Unit so I make a habit of building my reports with those groups.

Thank you all for your suggestions. I will revisit the report and apply the new information to the analysis.

OK. The burst fields were goups. Removed a comment from the report select - I never would have thought of that. Republished it three times with different report IDs. Tested the old report and it works so I copied it and modified it to meet the new report specs then published it to a new report ID and it still does not work. I think I will do something else and try again tomorrow. I am at the point of bursting it in a Crystal report and emailing it.