|
20 years ago I wrote a report designer/reporting suit in COBOL using Btrieve as database - I can search for the source code and send you if you want!?
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
COBOL? HAHAHA
Thanks, I needed a laugh.
If it's not broken, fix it until it is
|
|
|
|
|
COBOL lives.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: COBOL lives.
... in someone's mind.
If it's not broken, fix it until it is
|
|
|
|
|
Chris Maunder wrote: COBOL lives.
It scares me to read that coming from you, of all people.
Which vital part of codeproject.com does it run?
|
|
|
|
|
The really old bit.
cheers
Chris Maunder
|
|
|
|
|
Visions of a drooling, geriatric hamster, multiple IV's hooked to its body, stumbling on a rusted, urine-encrusted wheel come to mind.
Yes, I wanted that picture in my head this morning  .
Software Zen: delete this;
|
|
|
|
|
Show me someone who doesn't have code maintained this way and I'll show you someone new to the game or a liar.
For the sake of a little extra straw and newspapers it saves a rewrite.
cheers
Chris Maunder
|
|
|
|
|
Yeah, I know. I have a group of C++/MFC applications still being maintained using Visual Studio 2003.NET, because the Pointy-Haired Boss types don't want to spend the resources to do regression testing after we upgrade to a more recent tool set.
Like Visual Studio 2008  , which is what use for our current products.
Software Zen: delete this;
|
|
|
|
|
It does indeed, name your price you contractors.
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Kevin Marois wrote: Crysal Report....20 years ago they were great. $hit now.
No, they were $hit then, too.
Will Rogers never met me.
|
|
|
|
|
|
Have you looked at using RDLC? It's baked into Visual Studio, and apparently there's a ReportViewer that you can use with WPF.
http://msdn.microsoft.com/en-us/library/hh273267.aspx[^]
I'm using it with great success in an ASP.NET MVC app.
Jon Sagara
Some see the glass as half-empty, some see the glass as half-full. I see the glass as too big.
-- George Carlin
Blog | Twitter | Articles
|
|
|
|
|
Yeah its based on SSRS. Personally I really like it.
|
|
|
|
|
I wrote my own, it outputs to:
Laser
Matrix
Fax
Email
PDF
Excel
HTML
Text
SQL
And if anything is missing I just code it in.
|
|
|
|
|
You know you can print WPF, right?
So design your report in WPF, bind, print.
Bob's your proverbial Mother's Brother.
PooperPig - Coming Soon
|
|
|
|
|
Have you ever created a non-trivial WPF document? It's a tremendous memory hog, and leaks like a sieve. I have an in-house report generator that can create HTML or WPF docs. For a 5MB HTML document, the corresponding WPF doc is 400-500MB. Loading that into a viewer control takes several minutes (consuming 1G or more of memory), which brings the entire application to a screeching, page-faulting halt.
The gains from using WPF documents (data binding et al) aren't worth the costs.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: Have you ever created a non-trivial WPF document?
Yes
Gary Wheeler wrote: It's a tremendous memory hog,
Is it? I can't say I'd noticed - the WPF app I work on is a memory hog much worse in so many other ways, any WPF overhead is trivial by comparison!
Gary Wheeler wrote: leaks like a sieve.
Interesting - I've been doing some work on fixing memory leaks in our app - none (so far!) has been due to WPF
Gary Wheeler wrote: The gains from using WPF documents (data binding et al) aren't worth the costs.
with the possible exception of the fact that the OP is using WPF so may well have excellent WPF skills, existing forms and data binding that may suffice for his reporting requirements with perhaps a little tweaking.
Personally I'm a fan of exporting data to excel for reporting - let the report users tweak the raw data how they want - and provide templates if necessary
HTML is fine for the pretties, but rubbish if users want to play with the data
PooperPig - Coming Soon
|
|
|
|
|
My reporting class serves two purposes. One, I display the generated HTML in a browser control inside the app. Two, the HTML/XML can be written to a file and used elsewhere. The best example is our 'diagnostic report'. Instead of playing 20 Questions with a customer (or our field service folks), we have them send us a diagnostic report. It takes one click to generate. It's about 5-10MB of HTML that dumps application and Windows information._Maxxx_ wrote: Personally I'm a fan of exporting data to excel for reporting - let the report users tweak the raw data how they want - and provide templates if necessary
I'd use that method if I could, but it's beyond the skill set (or interest) for my customers.
Software Zen: delete this;
|
|
|
|
|
We use SSRS, both the RLD server version and the RDLC embedded in the apps, works well, has a WPF viewer (no Silverlight viewer though).
Oh and Roger is correct Crystal Reports were sh*t 20 years ago as well!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Create the reports in Ms Access, it's the easiest and fastest way to create reports and best reporting tool IMO.
|
|
|
|
|
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.
|
|
|
|
|
I use SQL Reporting and the Perpetuum Silverlight Report Viewer.
I'm very pleased with the results.
|
|
|
|
|
Fast-Report[^]
Used it for Delphi years ago. Still works. In fact, just built about 10 reports with it.
Available for .Net
Solid design, as I am able to run X reports, and collect each report separately into one final result (for preview and/or printing), and with some effort, you can get the page numbering (x of y) to be correct in either mode (each report starts a page 1 of Yn, or each report picks up where the other left off).
And the report "file" (.frp) is actually XML. I was able to tweak this outside of the report generator just fine.
One other great feature: find text works in the preview!
HTH,
Kirk Out!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
