>>Instead of creating the report as soon as the user says to, log this request with pertinent info to a table. When they hit distribute, then prompt for the printer, and execute the report creation to the printer they select.
>
>I thought of this and it's also quite complicated :( These jobs may be run on Friday and we want to distribute on Monday. The environment needed for report creation (tables, indexes, etc) may be already altered or deleted...
>
>I really don't see a normal solution to this problem. PDF idea is also quite complicated and would not work for printers, which don't allow graphics (Matrix printers)...

Use the CREATE VIEW command [this is not the SQL CREATE VIEW command] to create a snapshot of the Environment to a file. Use FileToStr() to then store this file to a memo field in your Log file. Use another memo field to store SQL query. Other fields to store UserID, ReportName.

When you are ready to distribute the report, use the SET VIEW TO command in a [private] SESSION class to restore that environment.

Other than that, I would say you and your organization need to have a conversation about modifying some business rules.