|
If your problem is… |
You need cViewSERVER to... |
|
Admin has to stay logged in to send reports |
Send reports from a service, rather than from an application. |
|
Data crashes are occurring. |
Spread your report distribution out, or schedule for off-peak times. |
|
Distributing reports is time-consuming |
Automate your report distribution. |
|
Inability to use the same report multiple
times with different parameters and/or destinations. |
Create distribution lists and customize who gets what. Then, send it
automatically. |
|
Inability to upgrade the network to handle
the increased report traffic. |
Spread your report distribution out, or schedule for off-peak times. |
Manual report distribution is:
- costly.
- labor-intensive.
- tying you to a rigid schedule.
|
Automate your report distribution. |
Reports, distributed manually, are:
- duplicated or redundant.
- inconsistently delivered.
- interrupted during delivery due to other demands.
- late.
- missing altogether.
|
Automate your report distribution. |
|
Re-using a report would make so much sense and save you loads of
time and money. But you don't have a way to do it. |
Distribute reports to whatever lists you want. You can set
parameters to use variations of the same report over and over. |
|
Security issues make it tough to admin report distribution. |
Send reports from a service, rather than from an application. |
|
Slow network performance. Can't afford to upgrade the network. |
Automate your report distribution. |
|
Timely reports with current information are needed. |
Schedule your report distribution for when users want to receive
reports--rather than for when you can find time to send them. |