We follow the same concept that bburnell has mentioned.
We have been converting all our old Access applications up into VB over the past 18 months. Many of these Access application really did nothing but display various reports. We recreated all the reports via SSRS in one big solution (one project inside the solution per "application" to keep things visually more appealing and easier to work with) and have them all running Server-side. We then constructed one big VB application that consolidates all the reports into a one-stop shopping location.
Many of those same reports can also be accessed from various other applications or even the server directly as well.
We find this much easier because you do not have to touch the app to update reports. You can make changes to the reports all day long and just redeploy them...As long as nothing from the application side (such as parameters) has changed, there is no need to even open the application project.
As stated by bburnell, our report server is the same as our primary data server...so if one was down, they'd both be down anyway. Might as well take advantage of the multiple-processor, huge RAM base that the server has and not rely on who-know-what PC to do the rendering. Also, wtih Server-sde reports, you can optionally set them to run via cached-modes and snapshots, which can greatly reduce server hits and processing if the report does not change much, such as daily sales figures.
Just my couple of pennies....
=======================================
People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. (Calvin from Calvin And Hobbs)
Robert L. Johnson III
CCNA, CCDA, MCSA, CNA, Net+, A+, CHDP
VB.NET Programmer