1.

Schedule a simple Report to export to HTML every weekday at specified times of the day.

2.

Schedule a number of reports as a "package" to export to HTML every Monday and Friday at specified times of the day.

3.

Schedule to create a specified folder on the first Monday of every month.

4.

Event-Based Schedule

Fire off and deliver reports automatically when an event occurs.  Here are some examples.

If a file exists If a file has been modified If a database record exists If a database record changes If an unread email is present	Advanced: If a new database record exists, use  the data in the record to send an email to a recipient Advanced: If an unread email is present use data in the email to create a new database record.

5.

Group a number of event-based activities and determine timing, order of execution and more

6.

Dynamic Schedule

SQL-RD will reel through a list of parameter values, generate a unique report for each value, and deliver each report to a unique destination (e.g. email address, folder, etc). Saves you from having to write and maintain multiple schedules.

Simple Dynamic Schedule Advanced Dynamic Schedule

7.

Dynamic Package

Same as Dynamic Schedules, but multiple reports to specified destinations.

Simple Advanced

8.

Drive all variables of your reporting requirements (parameters, destinations, output format, etc) from database tables and queries. Also package multiple reports, merge multiple excel sheets into one workbook, or pdf exports into a single pdf with bookmarks.

9.

Calendar

Create your own scheduling frequencies using Custom Calendars (e.g. 4-4-3).  Or use Exception Calendars to skip special days (e.g. public holidays)

Custom Calendar Exception Calendar

10.

Set up logon credentials for the reports.  Keep copies of exported reports for x days.

11.

How to tell SQL-RD what report parameter values to use.

12.

Retry x times on failure. What to do if the report "hangs". Take some action if the report returns no data.

13.

Destinations

SQL-RD will send your reports to a number of destinations.

Printer Fax Email	FTP Disk SMS (Cell phone text)

14.

Set up a number of destinations (email, printer, fax, SMS, folder and FTP) and use them over and over again.

15.

Output Formats

Learn how to quickly set up schedules to export to pdf, tiff, xls, and many more formats.  Also shown are output features e.g. custom report naming, zipping the export, zip encryption, deferred delivery, and lots more.

Acrobat (PDF) HTML (HTML) Lotus 1-2-3 (WK1) Lotus 1-2-3 (WK3) Lotus 1-2-3 (WK4) Lotus 1-2-3 (WKS) Microsoft Excel (XLS) Microsoft Word (DOC) Rich Text (RTF)	Data Interchange Format (DIF) Web Archive (MHTML) XML (XML) Character Separated (CSV) Text (TXT) TIFF (TIF) dBase II (DBF) dBase III (DBF) dBase IV (DBF)

16.

When the report has been delivered, run a batch file, update a database, send an email and more.

17.

Insert Constants (e.g. Yesterday's Date, CurrentScheduleName, ExportedFileName) to automate otherwise repetitive and mundane processes.

18.

User Management

Set up and manage and assign schedule to users Set up and assign users to a security group

19.

Set up SQL-RD to use MAPI to send emails.

20.

Integrating the NT service Exchange Server

Set up SQL-RD to use Exchange Server to send emails.

21.

Set up SQL-RD to use SQL-RDMail to send emails.

22.

Set up SQL-RD to send SMS text alerts.

23.

Set up SQL-RD to use SMTP to send emails.

24.

Set up SQL-RD to use GroupWise to send emails.

25.

Automatically backup the SQL-RD system and files.

26.

Set up SQL-RD to use the Application Scheduler.

27.

Set up SQL-RD to use the Windows (NT) Service.

28.

Address Book

Setting up Contacts Setting up groups Exporting & Importing	Editing Contacts & Groups Deleting Contacts & Groups

29.

Use smart folders to group schedules and to report on schedule activity

30.

Don't type the same password, email body, signature etc over and over again.  With User Defaults you can enter than once, and reuse them each time your write a schedule.

31.

Set up an audit trail showing activities that have happened in SQL-RD.

32.

Connect to and administer remote installations of SQL-RD from your PC.

33.

Set up folder housekeeping and other automated processes to help keep your system and pc robust and stable.

34.

Use multiple PCs to schedule hundreds of reports.  The "Master" controls a bank or "cluster" of PCs ("slaves") and instructs them what to run and when.  See how easy it is to set this up.

35.

The SQL-RD data (schedule info etc) is stored in a Access database locally.  Migrating to a SQL, Oracle or other ODBC compliant database gives you enterprise scalability and reliability - and gives you the ability to write triggers, stored procedures and add custom functionality.

36.

Migrate back to the local file system.  Useful if you know your server is going to be down for maintenance.