You need to install Excel on the server as well. Remember the interop
libraries are just wrappers around the actual Excel COM library.
BTW, automating Microsoft Office applications on server-side is not
recommended and nor supported. For more info, read
http://support.microsoft.com/kb/257757/
> Can anyone tell me why I am getting this error? It bombs on this line
> of my VB code:
[quoted text clipped - 5 lines]
> references added to my project but I still get this error. What am I
> missing?
Mel - 10 Aug 2007 18:42 GMT
> You need to install Excel on the server as well. Remember the interop
> libraries are just wrappers around the actual Excel COM library.
[quoted text clipped - 11 lines]
> > references added to my project but I still get this error. What am I
> > missing?
Yep, we did install Excel on the web server. If it's not supported
does that mean it absolutely can't be done? Is that the reason why I
am getting the error message, because it's not supported?
Mark Rae [MVP] - 10 Aug 2007 19:28 GMT
> If it's not supported does that mean it absolutely can't be done?
Yes.
> Is that the reason why I am getting the error message, because it's not
> supported?
The reason you're getting the error message is because it doesn't work,
which is also the reason why it's not supported...

Signature
Mark Rae
ASP.NET MVP
http://www.markrae.net
> Can anyone tell me why I am getting this error? It bombs on this line
> of my VB code:
> Public appExcel As New Excel.Application
Because server-side Office automation doesn't work:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q257757#kb2
You'll need to find a different method of integrating Excel into your
ASP.NET app - what are you trying to do exactly...?

Signature
Mark Rae
ASP.NET MVP
http://www.markrae.net
Mel - 10 Aug 2007 18:03 GMT
> > Can anyone tell me why I am getting this error? It bombs on this line
> > of my VB code:
[quoted text clipped - 8 lines]
> Mark Rae
> ASP.NET MVPhttp://www.markrae.net
The Excel spreadsheet is a calculator. It has a ton of formulas which
were written by a 3rd party vendor of ours. Instead of reinventing
the wheel and creating a new web page which incorporates all of those
same formulas I figured it was easier to just have Excel run in the
background with that spreadsheet open (for read only access). The
idea is, when the user changes an input field on the web page the
visual basic code changes the corresponding field in the spreadsheet
which is running in the background and just retrieves the results from
the spreadsheet and places them on the web page "outputs" section.
Then, as far as maintenance is concerned, if in the future any of the
calculations change we can just update the spreadsheet and no code
would need to be changed on the web site.
Mark Rae [MVP] - 10 Aug 2007 18:16 GMT
> I figured it was easier to just have Excel run in the background
Won't work, I'm afraid - Excel (like the rest of Office) just isn't designed
to be run like this...

Signature
Mark Rae
ASP.NET MVP
http://www.markrae.net
Mel - 10 Aug 2007 18:28 GMT
> > I figured it was easier to just have Excel run in the background
>
[quoted text clipped - 4 lines]
> Mark Rae
> ASP.NET MVPhttp://www.markrae.net
Seriously. That stinks. So what are my alternatives?
Mark Rae [MVP] - 10 Aug 2007 19:30 GMT
> Seriously. That stinks. So what are my alternatives?
http://www.aspose.com/Products/Aspose.Cells/Default.aspx
Says it supports VBA, though I've never used it in this way...

Signature
Mark Rae
ASP.NET MVP
http://www.markrae.net