Reporting System Setup

Setup Options > System Setup > Reporting

This improves report rendering by moving the XML into a temporary SQL database before binding the data to the .RPT file.

It also frees up resources on the client workstation by transferring processing tasks to the server. The server generates a .PDF file which is sent to the client machine.

This option doesn't require Crystal on the client machine; only an appropriate report reader (e.g. Adobe Acrobat Reader, SYSPRO Office Integration, Espresso).

When enabling this option for the first time, the Documents.XML files are copied to Documents_Server.XML. When you subsequently update printers for documents, the relevant file is updated (i.e. Documents.XML for client-side and Documents_server.XML for server-side printing).

If you switch between client-side and server-side reporting, the printers have to be re-configured.

This improves report rendering by moving the XML into a temporary SQL database before binding the data to the .RPT file. All the processing is completed on the client machine.

If you switch between client-side and server-side reporting, the printers have to be re-configured.

This initiates client-side reporting (as it was in prior versions of SYSPRO) binding the report to the .XML file on the client machine.

This indicates the address to the reporting host service (e.g. localhost:1979).

Enter the scheduler authentication user name (i.e. the Windows Task Scheduler permission that allows the operator to create and maintain schedules on the server).

Enter the scheduler authentication password (i.e. the Windows Task Scheduler permission that allows the operator to create and maintain schedules on the server).

This lets you purge the document print queue automatically.

Enter the number of days (up to 999) you want an item to remain in the queue before it is automatically purged.