I've spent the past few weeks looking into various reporting mechanisms that will enable our company to create automated Excel reports in a "better" way.
Currently, we're running a copy of Excel on the server and using VB.NET to create Excel objects through Interop. It works just fine (mostly), but I hate to keep running Excel on the server for the standard reasons.
Basically, I have two alternatives in mind, and I see pluses and minuses to both. I'm wondering if anyone has any experience with either, or has any advice in general.
First, I've been looking into SoftArtisan's OfficeWriter. I've heard good things about it, and it obviously takes the burden off of running Excel on the server. It also integrates with SSRS, which we'll definitely be using in the future. It's a clean solution, isn't terrible processor intensive, and the price isn't bad for the standard version (which is what we'd be interested in purchasing).
Second, we have a lot of old equipment sitting around. One of these old machines could be used as a "work horse" machine, whose job is basically to create the reports from a locally running copy of Excel. A user would request a report through an ASP page, and the request would send a message to the work horse machine that would create the Excel report, etc. This method wouldn't require any further purchase. The maintainability of this option seems to be a bit higher, though. The method also seems to be somewhat archaic.
I go back and forth between the two options. I can see goods and bads in each. Does anyone have any experience of this type that could help sway my decision either way?
Currently, we're running a copy of Excel on the server and using VB.NET to create Excel objects through Interop. It works just fine (mostly), but I hate to keep running Excel on the server for the standard reasons.
Basically, I have two alternatives in mind, and I see pluses and minuses to both. I'm wondering if anyone has any experience with either, or has any advice in general.
First, I've been looking into SoftArtisan's OfficeWriter. I've heard good things about it, and it obviously takes the burden off of running Excel on the server. It also integrates with SSRS, which we'll definitely be using in the future. It's a clean solution, isn't terrible processor intensive, and the price isn't bad for the standard version (which is what we'd be interested in purchasing).
Second, we have a lot of old equipment sitting around. One of these old machines could be used as a "work horse" machine, whose job is basically to create the reports from a locally running copy of Excel. A user would request a report through an ASP page, and the request would send a message to the work horse machine that would create the Excel report, etc. This method wouldn't require any further purchase. The maintainability of this option seems to be a bit higher, though. The method also seems to be somewhat archaic.
I go back and forth between the two options. I can see goods and bads in each. Does anyone have any experience of this type that could help sway my decision either way?
Comment