For @MarkKotyla and @bertowud at least:
Here is one I did and added 2 addl export variations (for sake of example). I had to remove the clients names and other identifying info. Also the .RPTs referenced in this report use a Silent Connect DSN instead of SOTAMAS90. I had that option because they only needed this to run from 1 location only (server).
The purpose was:
1) Auto-run their time consuming reports off-hours (I offered them Access pass through queries and use of SQL Server but they weren't interested)
2) Auto-Export to PDF, etc without any user input
A script was right solution for this client because it satisfied above, was less time consuming and cheaper than developing say a .Net app to do same, and most important could be scheduled via Windows Task Scheduler to run late at night (they didn't have K-Sync or Bus Alerts else we could've scheduled with that)
Basic concepts in the scripts are:
* Create variables to store the locations of the .RPT and final output
* Connect to Crystal Runtime object (MAS does it a lil differenty) and open the .RPT file
* Set the export options and do the export
These dev library links are VERY helpful for customizing your export type (PDF, XLS, CSV, etc) and export destination (Diskfile, Application, Exchange) and for customizing Excel and Exchange specific options:
http://tinyurl.com/3jvl2tl
http://tinyurl.com/3sj7qqh
http://tinyurl.com/3fdpcqx