>>>I briefly considered writing reports to (say) PDF files on the host and then somehow getting those files to the remote users, but that would be extra complication for no real gain.
>>
>>That was first idea that popped up and if user info can be coupled with email adress probably in long term one of the best maintainance saving options. Even if users have to download after being mailed a DL link, on the users side you are isolated pretty good from OS update harm.
>
>If asynchronous printing is OK then that could work well. OTOH if a customer is waiting for a receipt to print, not so much.

In the 2 page summary or application form you are probably almost always certain to be correct. The 200 page budget plan might be faster via PDF route, as you can add compression if not already working via http: - I have no idea if compression is already available via the comm channel to local printer. The ability to start again in case of paper jam or other mishaps is much better with a local file ;-)

And the speed of mail sending can be quite high: If that is an issue, $ spent there might be better investment than in $$$maintaining$$$ printer support via RDS and similar tools. Also think of the road wariors without or with broken small printer or the coming surther surge of mobile only clients wanting to print at EACH customer with the customers own HW ;-))