The excel import saga (as documented
here and
here continues...
I was successully OleDBReading in .XLSX and .XLSM files on a local machine and on a development server. I deployed the app to our UAT enviroment only to find that .XLSM imports would now fail with an "External table is not in the expected format"
error. Saving the failed file out as XLSX and importing that fixes the problem, but we're trying to limit the amount of manual work the users have to do to get their data into the system. Any idea if there are specific config differences that might cause
this behavior? Both are using the 64-bit JET driver.
(Was pulled away from this by assorted priority shifts, but it's back now.)
File size is the same in all locations and I've tried several different files with the same results.
The ACEEXCL.DLL version on my local machine is 14.0.6015.0; on the DEV and UAT servers it's 14.0.4760.0. Is there a package somewhere that will install the latest on the servers, or a straightforward method of doing so manually?
DonL
Member
1 Points
69 Posts
OleDB/Excel fails opening .XLSM, but only in some environments
May 07, 2012 07:02 PM|LINK
The excel import saga (as documented here and here continues...
I was successully OleDBReading in .XLSX and .XLSM files on a local machine and on a development server. I deployed the app to our UAT enviroment only to find that .XLSM imports would now fail with an "External table is not in the expected format" error. Saving the failed file out as XLSX and importing that fixes the problem, but we're trying to limit the amount of manual work the users have to do to get their data into the system. Any idea if there are specific config differences that might cause this behavior? Both are using the 64-bit JET driver.
TimoYang
Contributor
3732 Points
1275 Posts
Re: OleDB/Excel fails opening .XLSM, but only in some environments
May 09, 2012 02:26 AM|LINK
Maybe you've missed "IMEX"——try any of the following conn str：
<add name="xls" connectionString="Provider=Microsoft.ACE.OLEDB.12.0;Extended Properties='Excel 8.0;IMEX=1';" />
<add name="xlsx" connectionString="Provider=Microsoft.ACE.OLEDB.12.0;Extended Properties='Excel 12.0 Xml;IMEX=1';" />
<add name="xlsm" connectionString="Provider=Microsoft.ACE.OLEDB.12.0;Extended Properties='Excel 12.0 Macro;IMEX=1';" />
DonL
Member
1 Points
69 Posts
Re: OleDB/Excel fails opening .XLSM, but only in some environments
May 10, 2012 03:36 PM|LINK
Imex is in there - those are the exact connection strings I'm using.
Cathy Mi - M...
Member
741 Points
165 Posts
Microsoft
Re: OleDB/Excel fails opening .XLSM, but only in some environments
May 23, 2012 07:44 PM|LINK
Hi,
Is there any difference in the size of the file in the two different environments or does any .xlsm file fail?
What is the version of the ACE Excel driver in both environments (ACEEXCL.DLL)? Are they the same?
Thanks,
Cathy
DonL
Member
1 Points
69 Posts
Re: OleDB/Excel fails opening .XLSM, but only in some environments
Jun 08, 2012 02:58 PM|LINK
(Was pulled away from this by assorted priority shifts, but it's back now.)
File size is the same in all locations and I've tried several different files with the same results.
The ACEEXCL.DLL version on my local machine is 14.0.6015.0; on the DEV and UAT servers it's 14.0.4760.0. Is there a package somewhere that will install the latest on the servers, or a straightforward method of doing so manually?
Cathy Mi - M...
Member
741 Points
165 Posts
Microsoft
Re: OleDB/Excel fails opening .XLSM, but only in some environments
Jun 11, 2012 02:49 PM|LINK
Hi,
Here's a link to download the latest updates:
2692648 How to install the latest applicable updates for Microsoft Access http://support.microsoft.com/kb/2692648/EN-US
It contains a link to get the latest service pack for Office 2010 and then the latest hotfix package for Access Connectivity Engine 2010.
Thanks,
Cathy