Can Windows Task Scheduler Run and Export Crystal Reports?

Imagine an accounts assistant who exports an overdue-invoice report every Friday. You create a Windows task pointing at the RPT file, expecting the PDF to appear automatically. Instead, the designer opens or the task finishes without the file.

Windows has started what it was told to start. It has not been given a reporting workflow that loads the report, authenticates, supplies dates and exports it. Those responsibilities belong to the runner.

Keep the successful manual PDF as the reference. Your task needs to reproduce that result, including where accounts finds it and what should happen if the database is unavailable.

A maintained runner plus Windows Task Scheduler may be sufficient for one stable export. Configure the executable, arguments, working directory, trigger and execution account. Microsoft’s Task Scheduler documentation explains the trigger-and-action model.

The application still owns database access, parameter values, output validation and error reporting. A task’s successful launch is not the same as a complete report delivery.

CRD has its own scheduling engine, so another Windows timer is not required for an ordinary weekly CRD job. Where a central scheduler must start it, CRD also documents command-line execution of an existing schedule. Use one scheduling owner to avoid two Friday deliveries.

First run the chosen reporting executable outside Task Scheduler using the intended account and the exact invoice parameters. Confirm that it produces the correct PDF at a controlled folder. Resolve missing drivers or authentication prompts there before investigating the timer.

In Task Scheduler, create the trigger and program action. Set the account and working directory explicitly, then decide how overlapping runs and failures should be handled. Test the saved task under unattended conditions.

For a CRD-owned routine, prepare a Single Report schedule instead: choose the invoice RPT, relative reporting values, PDF and destination, then set the Friday recurrence. Add the failure notification and genuine no-data response appropriate to accounts.

Open the actual output after the scheduled run. Check an invoice you recognize and the reporting period; the task’s last-run result alone will not establish either.

If your central scheduler already coordinates Friday’s processing, it can start the prepared CRD schedule after the invoice load. Accounts keeps the file and delivery instructions in CRD while the central process owns the start condition.

"C:\Program Files (x86)\ChristianSteven\CRD\crd.exe" -s schedulename=FridayInvoices

Accounts should find the right overdue-invoice file without somebody opening the designer. A maintained runner can achieve that; CRD is useful when the parameters, exports and deliveries need to be managed together.

Compare CRD scheduling with your existing task using that same report. The Crystal Reports automation overview explains the additional workflow options.