Hi, I guess I don't understand the maintenance issues. Wouldn't you just add HTML files for every year or risk scenario? So, as long as you have write access to a browser folder, this year, you might have something like this: report_2010_r1.html rejport_2010_r2.html report_2011_r1l.html report_2011_r2.html report_2012_r1.html report_2012_r2.html report_2013_r1.html report_2013_r2.html ...and then next year you would add report_2014_r1.html etc, etc... As long as you keep your original datasets that were used to create the HTML files, you should be able to recreate any of the HTML files. Or, you could store the procedure results in an ODS DOCUMENT store, for archive purposes. Having the HTML tags and output in a SAS dataset just give you a different maintenance issue -- instead of 5K HTML files, won't you have 5K SAS datasets to maintain if you make a dataset for every HTML file? Once you had the HTML in a SAS dataset, how do you envision using these SAS datasets? Also, I don't understand what you mean when you say that the outputs are "published in our web platform only and are not accessed directly." If the HTML outputs are not accessed, why bother saving them? If you're using SAS/IntrNet or the BI Platform or stored processes, you could dynamically generate an output when you need it. Or you could have a macro program that took a year or a set of parameters to control the number of HTML files that were created. cynthia
... View more