Bye, byte Crystal Reports
-
I was just having a conversation yesterday with a co-worker. In all the organizations we have been in, no one has been able to get Crystal running without problems.
only two letters away from being an asset
I remember working for a company where we had been using crystal 7 in our app and it had been working flawlessy for ages until one client decided they wanted to upgrade their version of crystal. Basically the crystal support guy told us that the characteristic which had allowed our app to run flawlessly all this time was actually a bug in crystal which has now been fixed. Sorry, you app doesn't work any more but we won't be can't help you.
undefined
-
I was just having a conversation yesterday with a co-worker. In all the organizations we have been in, no one has been able to get Crystal running without problems.
only two letters away from being an asset
Mark Nischalke wrote:
n all the organizations we have been in, no one has been able to get Crystal running without problems
Same old story, CR is too black box, trying to make it for dummies.
We made the buttons on the screen look so good you'll want to lick them. Steve Jobs
-
I remember working for a company where we had been using crystal 7 in our app and it had been working flawlessy for ages until one client decided they wanted to upgrade their version of crystal. Basically the crystal support guy told us that the characteristic which had allowed our app to run flawlessly all this time was actually a bug in crystal which has now been fixed. Sorry, you app doesn't work any more but we won't be can't help you.
undefined
Oh yeah, that's why I wrote my own report engine, after upgrade from .net 1.1 to .net 2.0 things just stopped working, all the programs dependent on CR had to run under 1.1 until I reengineered them.
We made the buttons on the screen look so good you'll want to lick them. Steve Jobs
-
norm .net wrote:
I should market it, it's designed for developer by a developer.
Looks like you have some interest. When do you plan to have it available?
-
I've managed to engineer out all dependancies to Crystal Reports (I hate it X| ). They've had nearly 10 years to produce a Micrsoft Style Reporting Product and still can't get it right. Well I've written my own engine, which produces output for Laser, PDF, Text, Excel., Html and RAW output to Dot Matrix Line Printers. It's written entirely in .net with a few P/Invokes and a call to GhostWriter. The reports themselves can be written in any .net lingo. I should market it, it's designed for developer by a developer. So bye, bye Crystal can't say it's been great knowing you. :rose:
We made the buttons on the screen look so good you'll want to lick them. Steve Jobs
So, I have a question for you then. What other reporting engines have you tried? I've worked with a couple. Actuate, Accelio, and PostX most recently (although PostX doesn't count). It seems to me that all reporting engines start with a "cool" idea and then add feature upon feature until there's this big, tangled mess that still doesn't quite do what you want it to. Even working with simple stuff like XSL:FO has proved limiting. Has anyone worked with reporting software that they enjoyed working with? And not to rain on your parade, but the single most desirable thing to a business about reporting software is stability. You may be able to do everything in XSL:FO and make it look good, but if it's not on a solid server with scheduling and failover and has a company behind it that's accountable, business would be wise to not buy into it.
Logifusion[^] If not entertaining, write your Congressman.
-
I've managed to engineer out all dependancies to Crystal Reports (I hate it X| ). They've had nearly 10 years to produce a Micrsoft Style Reporting Product and still can't get it right. Well I've written my own engine, which produces output for Laser, PDF, Text, Excel., Html and RAW output to Dot Matrix Line Printers. It's written entirely in .net with a few P/Invokes and a call to GhostWriter. The reports themselves can be written in any .net lingo. I should market it, it's designed for developer by a developer. So bye, bye Crystal can't say it's been great knowing you. :rose:
We made the buttons on the screen look so good you'll want to lick them. Steve Jobs
Boo Yah! I too had a long and seething hatred for Crystal Reports that you can ony truly appreciate if you have spent years working with the product. Now that we're in the .net world there are oodles of great reporting products that at every point resolve some long outstanding dissapointment I had with Crystal. We use DevExpress, I've tried them all and highly recommend it.
-
Boo Yah! I too had a long and seething hatred for Crystal Reports that you can ony truly appreciate if you have spent years working with the product. Now that we're in the .net world there are oodles of great reporting products that at every point resolve some long outstanding dissapointment I had with Crystal. We use DevExpress, I've tried them all and highly recommend it.
-
So, I have a question for you then. What other reporting engines have you tried? I've worked with a couple. Actuate, Accelio, and PostX most recently (although PostX doesn't count). It seems to me that all reporting engines start with a "cool" idea and then add feature upon feature until there's this big, tangled mess that still doesn't quite do what you want it to. Even working with simple stuff like XSL:FO has proved limiting. Has anyone worked with reporting software that they enjoyed working with? And not to rain on your parade, but the single most desirable thing to a business about reporting software is stability. You may be able to do everything in XSL:FO and make it look good, but if it's not on a solid server with scheduling and failover and has a company behind it that's accountable, business would be wise to not buy into it.
Logifusion[^] If not entertaining, write your Congressman.
-
So, I have a question for you then. What other reporting engines have you tried? I've worked with a couple. Actuate, Accelio, and PostX most recently (although PostX doesn't count). It seems to me that all reporting engines start with a "cool" idea and then add feature upon feature until there's this big, tangled mess that still doesn't quite do what you want it to. Even working with simple stuff like XSL:FO has proved limiting. Has anyone worked with reporting software that they enjoyed working with? And not to rain on your parade, but the single most desirable thing to a business about reporting software is stability. You may be able to do everything in XSL:FO and make it look good, but if it's not on a solid server with scheduling and failover and has a company behind it that's accountable, business would be wise to not buy into it.
Logifusion[^] If not entertaining, write your Congressman.
-
Dustin Metzgar wrote:
Even working with simple stuff like XSL:FO has proved limiting.
limiting how?
"Alot of the people on this forum are incredibly stupid, thinking that the internet is real"
Score: 1.0 in the Soap Boxled mike
Well, one thing we have to do is print out letters that are stuffed into envelopes by rather large and expensive machines. On each page is a different folding mark to indicate to the machine where that page belongs. Once you create the FO, you're pretty much static. You can use markers to determine how many pages there are total, but there's nothing in FO that can conditionally draw a line depending on the page number (or anything, for that matter). So, you're essentially stuck.
Logifusion[^] If not entertaining, write your Congressman.