Don't set the connection string property. Set the ExcelFilePath property. I find that it causes fewer headaches than trying to build a string for the connectionstring, since unlike the other connectors, the Excel connection string has several parameters that you can use, only one of which is the actual file path.
I had the same problem. I searched for an hour to find the answer, and this worked! Thank you 🙂
For SQL 2016 none of the above worked; I right-clicked the connection manager > paramaterize, and that solved all of the issues trying to use both the connectionstring and ExcelFilePath properties...
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply