Alternatively, gin something up in a cross-platform toolkit.

I'm for a LaTeX or similar templetized system myself.

These were some of the problems I ran into:

\r\n
• It's not command-line scriptable. Not without buying an expensive product, at any rate, and even then, limited. This based on scanning docs (went through all the CR books at Staceys, an excellent tech bookstore in San Francisco), and Google, and Google Groups, and several CR developers I talked to. Best I can tell, it's an "in your face only" type of tool.
\r\n\r\n
• Multi-user deployment requires multiple licenses or licenses (CALS?, CACLS?). This gets expensive, fast.
\r\n\r\n
• In the process it was deployed at the last place I was at, there were some 32+ manual steps necessary to prepeare and deliver a report, occuring over the course of 40 minutes, requiring a button-presser to be there for the whole schmeer. I figure it was work that could have been substituted by a shell script or makefile similar to that I use for my resume production -- a day or so to set up and test, probably triggered automatically by a mail filter rule, held for QC review, then released.
\r\n\r\n
• In the course of reviewing the issues in my first point, I kept hearing about how fundamentally limited CR is. Yes, you can get some pretty stuff output Q&D, but extending this to useful facilities was at best dificult. Definite PHB appeal, at the cost of real capabilities.
\r\n\r\n