Post reply

Error when attempting to Dynamic set the Connection String to an Excel OLE DB DEstination Connection

  • November 15, 2011 at 10:31 am

    #1408059

    Hi,

    I can create the connection in 2005. That is not what the post was intended to be about.

    The thread is about dynamically setting the connection string.

    I had other issues when I switched to 2008.

    Glad you figured out what you were trying to do.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • November 16, 2012 at 11:07 am

    #1559886

    kramaswamy (11/8/2011)

    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 🙂

  • April 18, 2018 at 3:52 pm

    #1987433

    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