<div>
Number of things it could be, but right off permissions pop into mind. &nbsp;May sure you have access to the directory (and make sure you check the user that is actually running the process).<br />
<br />
Second would be the connect string.....pathing is correct?<br />
<br />
Jim.
</div>


<div>
permissions are all set I think. we run it from the mydocs folder. connection string is also good, pointing to our in-house sharepoint server. <br />
<br />
just for clarity's sake I want to point out that both the working and non-working instances are run from the same user, on the same machine &amp;&nbsp;login. basically if I copy the non-working excel file to a mapped drive and then open from it the mapped drive, it works. no change in the excel file at all, just the location of the file. very weird.
</div>


<div>
I think I totally mis-read your question.<br />
<br />
Let me make sure I go this straight:<br />
<br />
1. You open Excel on the local station.<br />
<br />
2. If you open the spreadsheet from a network drive, it works.<br />
<br />
3. If you copy that same spreadsheet to the local drive, then open it, it fails?<br />
<br />
First thing I'd do is zip the spreadsheet file, then copy the .zip to the local station and unzip. &nbsp;This will give you a CRC check on the file and your assured it's 100% accurate. &nbsp; While it's been quite some time, I've seen bad NIC drivers mess up a file.<br />
<br />
Along the same lines; anti-virus. &nbsp; A network file might not be getting scanned on open, but a local file might. &nbsp; Try disabling anti-virus for the above test.<br />
<br />
If that gets you now where, post the connection string your using and I'll think about it some more in the mean time.<br />
<br />
Jim.
</div>


<div>
Windows 8.1 64bit O/S. I disabled 3rd-party A/V (webroot), native windows defender already off. &nbsp; Zipped, copied, extracted XLSM (macro-enabled) Excel with no luck. It's not an issue with macro-enabling, as all of the code runs inside VBA. Its been this way for years. <br />
<br />
attached is a screen shot of the code, and error message. did a lot of research online. cant find an explanation or resolution of why the same file would work from a network drive. Error occurs when the connection is opened. tried both http &amp;&nbsp;https, so i don't think it is a certificate issue. Not sure why the error is &quot;invalid argument&quot;, as the arguments in the connection string do not change depending on the source of the file. my guess is that this is the closest error in the library. I believe that the network location is considered &quot;trusted&quot; (excel will at times prompt to trust a network file). <br />
<br />
doesn't matter what server i place the file on, i can run the VBA from any mapped drive. We have a few Windows servers, and a Ubuntu Server, and they all work. Curiously, if i run from a working mapped drive, but instead use UNC naming convention to access the file (&quot;\\&lt;server&gt;\&lt;shared directory&gt;&quot;), then the VBA fails at the connection. <br />
<br />
I am starting to wonder if it is perhaps an issue with the sharepoint server, and that SP is refusing the connection, though i cant imagine why it matters the location of the file, especially the C: drive.<br />
<a href="https://filedb.experts-exchange.com/incoming/2015/12_w50/1051804/VBA-Error.png" target="_blank" class="file-inline" title="shows the VBA code and error. (36 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>VBA-Error.png</a>
</div>


VBA-Error.png

<div>
i checked IE, and the site is in the Local Intranet Zone (this comes from a GPO on the server), and I also looked at IE's security settings for that zone, and don't see anything that would disrupt the &nbsp;connection as described. <br />
<br />
I then also looked at Excel's Trust Center settings, and even toggled a few, to no avail. i also added the source folder of the local drive as a Trusted Location. Still no luck.<br />
<br />
But, i ran the file locally from another PC, one that has Excel 2013 installed, and it is working flawlessly. I of course neglected to mention that some of the PC's, including mine, use Excel 2016. Barring some other difference on the working pc, my guess is that Excel 2016 has something to do with the problem. It appears that the Office 2016 installation drops a new version of ACEOLEDB.DLL, which is the Microsoft.ACE.OLEDB library file. There are a few versions in C:\Program Files (x86)\Common Files\Microsoft Shared, under the various Office XX folders, and my guess is that the PC picks the latest ACEOLEDB.DLL file if you open it locally, and an earlier version if you open the file from the network. Or some variation of that. This is probably due to how the various versions of ACEOLEDB.DLL installed are registered in registry. This will probably be addressed in an Office 2016 update. <br />
<br />
so in the end, i guess the 90's called, and they are looking for our old friend, &quot;DLL Hell&quot;.
</div>


<div>
Sounds like, great detective work!<br />
<br />
&lt;&lt;and my guess is that the PC picks the latest ACEOLEDB.DLL file if you open it locally, and an earlier version if you open the file from the network. &gt;&gt;<br />
<br />
Seems odd that it would do that, but I know references do auto update to the latest and it may not be doing that in a specific case.<br />
<br />
You can check that by opening the files as you are doing now, then opening the VBA editor and check the reference version that's listed.<br />
<br />
Jim.
</div>


<div>
BTW, I know Office 2016 has a number of issues, so I think your onto something in that regard.<br />
<br />
Jim.
</div>


<div>
I don't recall setting a point value, &nbsp;but your IE comment is what led to the solution, so thanks for staying with me on this one!
</div>


<div>
I ran into this exact issue again, when we migrated to a Sharepoint 2016 server, and when debugging the updated connection references (on a local machine), and getting &quot;invalid argument&quot;. I spent days trying to track down my issue. Imagine my surprise when finding this article 4 1/2 years later as the most exact description of my problem, only to realize that this was MY post!. <br />
<br />
so, same issue: if i run the file locally, no dice, opening the connection complains of &quot;invalid argument&quot;. If i copy it to a network drive, then it works. There is no error when the connection opens. <br />
<br />
On the machine(s) i was now testing, there is only one copy of ACEOLEDB.DLL, so my earlier supposition is now proven false. And, apparently not enough people have had this issue, because the file (version 16.0.4266.1001) hasn't been updated since 7/31/2015.
</div>


<div>
<div class="content wysiwyg-content">
I am stumped by this one. I have some VBA code in an Excel file that uses Microsoft.ACE.OLEDB.12.0 to retrieve a row from a SharePoint 2010 list. If I open the Excel file from a mapped drive and run the code, it works flawlessly. If I copy the working Excel file to my local hard drive and run the code, i get an exception &quot;Invalid Argument&quot; when the connection is opened.
</div>
</div>


I am stumped by this one. I have some VBA code in an Excel file that uses Microsoft.ACE.OLEDB.12.0 to retrieve a row from a SharePoint 2010 list. If I open the Excel file from a mapped drive and run the code, it works flawlessly. If I copy the working Excel file to my local hard drive and run the code, i get an exception "Invalid Argument" when the connection is opened.

Microsoft.ACE.OLEDB.12.0 works on and Excel file stored on a network drive, not if the Excel file is run from local C drive.

Microsoft Excel topics include formulas, formatting, VBA macros and user-defined functions, and everything else related to the spreadsheet user interface, including error messages.

Microsoft Excel

Visual Basic for Applications (VBA) enables building user-defined functions (UDFs), automating processes and accessing Windows API and other low-level functionality through dynamic-link libraries (DLLs). VBA is closely related to Visual Basic and uses the Visual Basic Runtime Library, but it can normally only run code within a host application rather than as a standalone program. It can, however, be used to control one application from another via OLE Automation. VBA is built into most Microsoft Office applications.