Reports can be printed locally, using the Print option on the menu bar. They can also be batch printed from a server-based queue, e-mailed to system users and roles, and saved in different file formats. For Crystal Reports, the Report daemon handles these reporting requests and manages server-side reporting.

The Report daemon can be run on a server other than the main application server. This lets you schedule batch reporting without affecting application performance. The Report daemon is managed and monitored by the .NET Report Service, which is installed as an additional service on the application server.

The .NET Report Service handles the server-side reporting functions, including starting and stopping the Report daemon, and daemon activity errors are displayed as Windows log events. Request processing errors are displayed in the Report daemon monitor screen. See QAD System Administration User Guide for more details on the Report daemon.