Great link!

We have Data Driven subscriptions, with a master list of subscripbers, and another table for each report, with comments, parameters, etc.. Joined together, they make 'the list' for any scheduled subscription. We have a flag on the master list (Y/N) used to disable all subscriptions for a user. I could see adding a similar flag to the report table. Since most of our reporting is weekly, a job could easily be scheduled to update the flag prior to the scheduled run.

The one issue I see - if a blank report is sent, when you do have an issue, the user is likely to ask 'where is my report'. If it comes sporadically, you may not know you are having problems.

Greg E