|
| Workflow | Data | SQL | Documents | Automation | QODBC | CDOSYS | Reports | Home |
|
Crystal Reports and SQL Reports Typical Client Requirements Solution Scenarios
I have been on several development teams that tended to relegate the writing of reports to the newest and youngest team member. But over the years I increasingly think this is a bad idea. It always seems to me that software vendors build their detail reports first and may not get much farther. Generally, the more useful the report, the more work involved in building it. In particular, summary and exception reports can be quite complex and can require highly advanced skills to build. I now see reports (and automation) as being the real opportunities to harvest the greatest return on investment for all the hard work already done. I like to say that any report longer than 10 pages is probably not very helpful. I like to ask users where their time really gets spent, and then I look for opportunities to "spoil" them. This is part of the quid pro quo I discuss elsewhere. To bring a long-run improvement to certain staff within an organization, I usually need to be able to pester them upfront to clarify requirements. This is a catch 22 since I am probably trying to help them precisely because they are already so busy. So, if I can knock off a couple reports along the way that helps them immediately, it typically goes a long way to earning trust during a larger effort.
|
|
© 2002-2010 Breeze Easy, Inc. All Rights Reserved |