Originally posted by: chronodekar
Originally posted by: KLin
Originally posted by: chronodekar
Umm... why will a user need a report? All they would need is a manual or something, right? Or is it some kind of bug-reporting thing ?
One of our clients run a a tour bus chartering business. the company I work for developed a custom C# application using SQL Server as the backend database to allow them to manage customer orders, employee labor, bus maintenance, etc.
In this application are many reports designed using crystal reports for the users to run (labor efficiency reports, open order reports, etc.). These are user defined reports to allow them to run their business more efficient.
We have another client that uses a c# application we developed to print out pallet tags for their finished good product. The pallet tag is a crystal report.
Starting to make sense now?
Things are beginning to make sense to me now.
I think what bugged me was, Why bother with a whole new tool for the purpose? I mean, why not just export to excel directly or something?
Ignoring the benefits/side-effects of the above suggestion, I have a much better idea of crystal reports now.
Hmmm... to me, a report is more useful if it's interactive. That should not be too hard. And we see something similar with many web-applications these days anyways.
Thanks, mate !! :thumbsup: