WPF Reporting
-
I posted a question [^]about WPF reporting. I got a few answers and I've been looking at them. 1) I've decided against Telerik after their Tech Support told their report suit only works if you purchase their Control suite also. 2) Infragists... NO! Used their crap in the past and I won't go back. Besides, I can't find a demo to try. Not a same to run... a demo I can download and work with. 3) CodeReason[^]... Looks promsing, but I downloaded it and I don't see any kind of designer(????) 4) Crysal Report....20 years ago they were great. $hit now. This got me thinking... what happened to the days of easy reporting. It used to be simple. Is it just me or has reporting gotten REALLYL complicated?
If it's not broken, fix it until it is
-
If your reports aren't that complicated, I don't see the problem with generating HTML, as others have suggested. I have an in-house reporting class that uses this approach. It generates HTML for readable documents and XML for import/export, both from the same report specification. While the HTML isn't fancy, that's only limited by your skill at CSS.
Software Zen:
delete this;
So many choices. Html/css, xml/xslt, word templates and vbscript (or vba if you have an old version). Excel etc.. I use the Office api to generate Word docs in C#.
I may not last forever but the mess I leave behind certainly will.
-
- Output data to Excel (use ClosedML from codeplex) 2) Tell users to go wild colouring in the resulting spreadsheet however they like
-
- Output data to Excel (use ClosedML from codeplex) 2) Tell users to go wild colouring in the resulting spreadsheet however they like
Excel is what we do now for reporting. Very flexible for the user who has to work with it. We've used Crystal Reports in the past; it's really no good anymore!
-
Kevin Marois wrote:
Crysal Report....20 years ago they were great. $hit now.
No, they were $hit then, too.
Will Rogers never met me.
I agree!
-
I posted a question [^]about WPF reporting. I got a few answers and I've been looking at them. 1) I've decided against Telerik after their Tech Support told their report suit only works if you purchase their Control suite also. 2) Infragists... NO! Used their crap in the past and I won't go back. Besides, I can't find a demo to try. Not a same to run... a demo I can download and work with. 3) CodeReason[^]... Looks promsing, but I downloaded it and I don't see any kind of designer(????) 4) Crysal Report....20 years ago they were great. $hit now. This got me thinking... what happened to the days of easy reporting. It used to be simple. Is it just me or has reporting gotten REALLYL complicated?
If it's not broken, fix it until it is
I have looked at a number of report writers for simple reporting needs. I have been using the Windows Forms Report Viewer Control 2012. This is a local version of SSRS with less features but adequate. The Report Viewer in VS2013 is the same as SSRS with some special new controls. I would recommend the control for simple reports. There is also a web version of the control.
Robert Neal
-
I posted a question [^]about WPF reporting. I got a few answers and I've been looking at them. 1) I've decided against Telerik after their Tech Support told their report suit only works if you purchase their Control suite also. 2) Infragists... NO! Used their crap in the past and I won't go back. Besides, I can't find a demo to try. Not a same to run... a demo I can download and work with. 3) CodeReason[^]... Looks promsing, but I downloaded it and I don't see any kind of designer(????) 4) Crysal Report....20 years ago they were great. $hit now. This got me thinking... what happened to the days of easy reporting. It used to be simple. Is it just me or has reporting gotten REALLYL complicated?
If it's not broken, fix it until it is
I'm coming in late on this discussion, but I was wondering if you looked at all at Windward? www.windward.net. Designer sits in MS office, so document formatting is as simple as using the office tools. Wizards connect to one or more data sources.