Hi Jeff,

As for the size of the stylesheet, it's roughly the same size as the html document it produces minus the data - which is as it should be.

I think that the use of xml and xsl is at the absolute centre of what the article was about (and not an addition to the discussion.)

If there are corners to be cut, I'd suggest (and I can hear you groan as I write this) a 2 line CLR function which takes an xsl, xml and returns the transformed document. That enables to you to do all this without troubling SSIS.

I have to say that one of my top pet hates is seeing html constructed with T-sql.

I note, Jeff, that you have a preference - and it is your right - for doing everything that can possibly be done with SQL with SQL. The result is that you can do some pretty crazy things with SQL with leave me for one breathless if not speechless. But I would argue that for generating html especially sophisticated html is either the job of an ASP application or why not take advantage of the xml functionalities in SQL and transform the result with XSL, as Paul has done. (Horses for courses?)

I include a link to articles [/url]I've written in a similar vein - which I fear you may hate! But just so you know precisely where I'm coming from!

Best regards,

David McKinney.