Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
lmnorms
8 Posts |
Posted - 2009-03-06 : 14:42:32
|
Hello,I currently have a VB.Net program that connects to a excel program.Works great locally but when I run a scheduled job through reportmanager on the server; I get an error. The error is: Comexception(0x800A03EC) "FilePath\File" Could not open excel.I understand that this is a common exception for running theInterop.Excel.My questions are:1. Can this error be fixed? I have not found any research thatsupports this.2. Would it be better if I switched to a ODBC connection to read thruthe excel file via an sql query?Thank you in advance for your comments. I apologized if this is the wrong forum for this question, I didn't know where else to put this topic. Patrick |
|
darkdusky
Aged Yak Warrior
591 Posts |
Posted - 2009-03-09 : 10:39:27
|
There are lots of examples in this forum of Excel to SQL Server e.g http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=49926If your report is also using SQL Server e.g. Reporting Services etc then you should be able to call a procedure in your report to read the Excel file. Alternatively you could set up a SQL Server scheduled job / SSIS to import the excel file to a table and have report just read from the table. |
 |
|
lmnorms
8 Posts |
Posted - 2009-03-09 : 16:31:34
|
Nope, still getting error when I let an automated product like Report Manager or Win Automation run the VB.net program. I even tried to change to OLEDB to read the excel workbook and local it worked but still no luck with automation. I welcome any ideas. |
 |
|
|
|
|