Crystal Reports 10
-
...I just saw the ad on your page, maybe it would also be good to allow us to leave some comments under the page advertising Crystal Reports 10. I could say I lot about the monster that you can not use in small projects, complicated binding (especially under the .Net), rampaging licensing, amateur exporting etc. While it is good for big projects that center around the print previewing and reporting, almost all other projects that need accasional reporting would find it an overkill to use CR. A classical example of a nice little reporting tool becoming a monster...and an ugly one. TO MICROSOFT -> please get some programmers to re-code and make available the Access reports for Visual Studio 6, Visual Studio .Net etc.
-
...I just saw the ad on your page, maybe it would also be good to allow us to leave some comments under the page advertising Crystal Reports 10. I could say I lot about the monster that you can not use in small projects, complicated binding (especially under the .Net), rampaging licensing, amateur exporting etc. While it is good for big projects that center around the print previewing and reporting, almost all other projects that need accasional reporting would find it an overkill to use CR. A classical example of a nice little reporting tool becoming a monster...and an ugly one. TO MICROSOFT -> please get some programmers to re-code and make available the Access reports for Visual Studio 6, Visual Studio .Net etc.
While I've never used Ver. 10, I've used Crystal Reports since 7.0 through 8.5 and for the most part it's a nice product. And, I don't think it's overkill as they have always made it (fairly) easy to use. However it does have its issues that I think hinder it.
-
It has always been buggy. It has quirks that will drive you nuts until you figure what's going on. And, sometimes it can corrupt .rpt files just by editing the things in the designer.
-
Its documentation sucks - they really need to improve in that area. While, it's straightforward to use CR, finding out how to do it in the first place (or learning something new) is a nightmare.
-
I don't mind the licensing issues (implementation that is), but it is way overpriced for what it does.
Jeremy Falcon
-
-
...I just saw the ad on your page, maybe it would also be good to allow us to leave some comments under the page advertising Crystal Reports 10. I could say I lot about the monster that you can not use in small projects, complicated binding (especially under the .Net), rampaging licensing, amateur exporting etc. While it is good for big projects that center around the print previewing and reporting, almost all other projects that need accasional reporting would find it an overkill to use CR. A classical example of a nice little reporting tool becoming a monster...and an ugly one. TO MICROSOFT -> please get some programmers to re-code and make available the Access reports for Visual Studio 6, Visual Studio .Net etc.
I agree, we used it for years and dumped it recently because of the ongoing re-distribution nightmare of their own creation, bloated size, horrible licensing and pricing for the report designer component and last but not least the fact that we switched to .net for all our new apps and there are much better products out there for .net based reporting that suffer from none of the above problems, are cheaper and are built *in* .net making them a "slam dunk" choice over Crystal Reports. We tried to work with Crystal for years and despite having a rather large distribution for our software were never able to wangle a deal with them better than the going off the shelf price for their report designer component. They are a company that is really focused on large enterprise and now more so than ever, nothing really surprising I guess considering that aspect. Let's leave Microsoft out of this one shall we?;) There are too many other nice products for .net that I would hate to see stomped.
An election is nothing more than the advanced auction of stolen goods. - Ambrose Bierce -
...I just saw the ad on your page, maybe it would also be good to allow us to leave some comments under the page advertising Crystal Reports 10. I could say I lot about the monster that you can not use in small projects, complicated binding (especially under the .Net), rampaging licensing, amateur exporting etc. While it is good for big projects that center around the print previewing and reporting, almost all other projects that need accasional reporting would find it an overkill to use CR. A classical example of a nice little reporting tool becoming a monster...and an ugly one. TO MICROSOFT -> please get some programmers to re-code and make available the Access reports for Visual Studio 6, Visual Studio .Net etc.
We dumped it for SQL Server 2000 Reporting Services[^]
Promise only what you can do. And then deliver more than what you promised.
This signature was created by "Code Project Quoter". -
...I just saw the ad on your page, maybe it would also be good to allow us to leave some comments under the page advertising Crystal Reports 10. I could say I lot about the monster that you can not use in small projects, complicated binding (especially under the .Net), rampaging licensing, amateur exporting etc. While it is good for big projects that center around the print previewing and reporting, almost all other projects that need accasional reporting would find it an overkill to use CR. A classical example of a nice little reporting tool becoming a monster...and an ugly one. TO MICROSOFT -> please get some programmers to re-code and make available the Access reports for Visual Studio 6, Visual Studio .Net etc.
-
We dumped it for SQL Server 2000 Reporting Services[^]
Promise only what you can do. And then deliver more than what you promised.
This signature was created by "Code Project Quoter". -
...I just saw the ad on your page, maybe it would also be good to allow us to leave some comments under the page advertising Crystal Reports 10. I could say I lot about the monster that you can not use in small projects, complicated binding (especially under the .Net), rampaging licensing, amateur exporting etc. While it is good for big projects that center around the print previewing and reporting, almost all other projects that need accasional reporting would find it an overkill to use CR. A classical example of a nice little reporting tool becoming a monster...and an ugly one. TO MICROSOFT -> please get some programmers to re-code and make available the Access reports for Visual Studio 6, Visual Studio .Net etc.
-
...I just saw the ad on your page, maybe it would also be good to allow us to leave some comments under the page advertising Crystal Reports 10. I could say I lot about the monster that you can not use in small projects, complicated binding (especially under the .Net), rampaging licensing, amateur exporting etc. While it is good for big projects that center around the print previewing and reporting, almost all other projects that need accasional reporting would find it an overkill to use CR. A classical example of a nice little reporting tool becoming a monster...and an ugly one. TO MICROSOFT -> please get some programmers to re-code and make available the Access reports for Visual Studio 6, Visual Studio .Net etc.
-
While I've never used Ver. 10, I've used Crystal Reports since 7.0 through 8.5 and for the most part it's a nice product. And, I don't think it's overkill as they have always made it (fairly) easy to use. However it does have its issues that I think hinder it.
-
It has always been buggy. It has quirks that will drive you nuts until you figure what's going on. And, sometimes it can corrupt .rpt files just by editing the things in the designer.
-
Its documentation sucks - they really need to improve in that area. While, it's straightforward to use CR, finding out how to do it in the first place (or learning something new) is a nightmare.
-
I don't mind the licensing issues (implementation that is), but it is way overpriced for what it does.
Jeremy Falcon
I can't agree more! It has always been buggy That's by far the worst thing of CR. If they only could make it running the way it should. btw don't talk about deployment of CR...
"All languages allow you to write crap code, VB just makes it easier (IMO)." Michael P Butler
-
-
While I've never used Ver. 10, I've used Crystal Reports since 7.0 through 8.5 and for the most part it's a nice product. And, I don't think it's overkill as they have always made it (fairly) easy to use. However it does have its issues that I think hinder it.
-
It has always been buggy. It has quirks that will drive you nuts until you figure what's going on. And, sometimes it can corrupt .rpt files just by editing the things in the designer.
-
Its documentation sucks - they really need to improve in that area. While, it's straightforward to use CR, finding out how to do it in the first place (or learning something new) is a nightmare.
-
I don't mind the licensing issues (implementation that is), but it is way overpriced for what it does.
Jeremy Falcon
Haven't played with 10 but if you're happy with 8.5 then whatever you do, DO NOT upgrade to 9!!!
-
-
Haven't played with 10 but if you're happy with 8.5 then whatever you do, DO NOT upgrade to 9!!!
We use 8.0 and are far from happy with it. The Viewer control takes loads of memory but wont give it back :mad: We are looking at upgrading (in the vain hope that the next version or the next version after that may be better). Unfortunatly we are not using .net yet and there are few other alternatives. Jon
-
...I just saw the ad on your page, maybe it would also be good to allow us to leave some comments under the page advertising Crystal Reports 10. I could say I lot about the monster that you can not use in small projects, complicated binding (especially under the .Net), rampaging licensing, amateur exporting etc. While it is good for big projects that center around the print previewing and reporting, almost all other projects that need accasional reporting would find it an overkill to use CR. A classical example of a nice little reporting tool becoming a monster...and an ugly one. TO MICROSOFT -> please get some programmers to re-code and make available the Access reports for Visual Studio 6, Visual Studio .Net etc.
<Shameless plug> If you don't like CR, you can buy my product, EasiReports[^], and help support a fellow CPian :-D It's small, cheap and comes with a year's support and upgrades. The next version will include the full source code, and support for any datasource. </Shameless plug> ---------------------------- Be excellent to each other :)
-
I can't agree more! It has always been buggy That's by far the worst thing of CR. If they only could make it running the way it should. btw don't talk about deployment of CR...
"All languages allow you to write crap code, VB just makes it easier (IMO)." Michael P Butler
Maximilian Hänel wrote: btw don't talk about deployment of CR... LOL! I know what you mean, and those generic error messages don't help when you're trying to figure the problem out. Jeremy Falcon