Long story short:
I found a way to print reports from WebSpeed. I use WebSpeed just as the user interface, creating a record in a table which just consists of fields for the report parameters, including the report name.
A UNIX cron job runs every minute in the background, which starts a (non-WebSpeed) Progress session. It checks to see if there are any records in the report queue table, and if so, collects the parameters, deletes the record, and runs the requested report. Because the report is not run by WebSpeed, it can print to a printer , or email the user an attached Excel CSV file.
I've always felt constrained by WebSpeed's inability to print documents, or email the users the data they are looking for. This solution isn't perfect, there can be up to 60 seconds before the report begins to run, but it's a major breakthrough in my book.
I found a way to print reports from WebSpeed. I use WebSpeed just as the user interface, creating a record in a table which just consists of fields for the report parameters, including the report name.
A UNIX cron job runs every minute in the background, which starts a (non-WebSpeed) Progress session. It checks to see if there are any records in the report queue table, and if so, collects the parameters, deletes the record, and runs the requested report. Because the report is not run by WebSpeed, it can print to a printer , or email the user an attached Excel CSV file.
I've always felt constrained by WebSpeed's inability to print documents, or email the users the data they are looking for. This solution isn't perfect, there can be up to 60 seconds before the report begins to run, but it's a major breakthrough in my book.