We Keep Coding

c# trouble opening excel xlsx file in datatable

I can easily open xls file with this code:
System.Data.OleDb.OleDbConnection theConnection = new System.Data.OleDb.OleDbConnection("provider=Microsoft.Jet.OLEDB.4.0;data source=C:\\Users\\us269229\\Desktop\\workbook.xls;Extended Properties=\"Excel 8.0;HDR=NO;IMEX=1;\"");
theConnection.Open();
however, I cannot open xlsx files. With the above code I get the following error:
External table is not in the expected format.
so I tried the following if the extension is xlsx:
System.Data.OleDb.OleDbConnection theConnection = new System.Data.OleDb.OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\\Users\\us269229\\Desktop\\workbook.xlsx;" + "Extended Properties=\"Excel 12.0 Xml;HDR=YES\"");
theConnection.Open();
however, with this I get this error:
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local
machine.
I did download and install AccessDatabaseEngine_X64.exe, but this did not clear my error.
Any help would be appreciated - thanks in advance

I think you need to Install "The 2007 Office System Driver: Data Connectivity Components.".
Source:
'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine

External table is not in the expected format. MS office not installed. Creating xlsx file using C#

Trying to create excel file from C#.
Challenges
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
Resolved using this
Now stuck on
An exception of type 'System.Data.OleDb.OleDbException' occurred in System.Data.dll but was not handled in user code
Additional information: External table is not in the expected format.
Searching a lot since my morning. No results yet.
OS- 64 bit, MS Office not installed, AccessDb file given in path above is installed.
Can I create Oledb connection without having MS Office?

After lot of hit and try I finally found a wall where I was hitting my head.
External table is not in the expected format.
This error not only means that you have some problem with driver. It can also means you file format is unrecognised.
This was because, I was creating xlsx file programatically.
string pathWithExtension=location + fileName+DateTime.Now.ToString("yyyyMMddss") + ".xls";
if (!File.Exists(pathWithExtension))
{
File.Create(pathWithExtension).Close(); //Dont create this file. Won't create valid xlsx file
//pathWithExtension = "C:/myFile.xlsx"; try using some template like this
ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=" + pathWithExtension + ";Extended Properties='Excel 12.0;HDR=YES'";
//call con.Open() throws above exception saying "External file is...."
This was because when I was creating xlsx file manually, it was not an
actual xlsx file. It was just a simple txt file with only give
extension as xlsx

Import Excel 2013 to vs, Microsoft ACE.OLEDB.12.0 is not registered on the local Machine

Creating a form application in vs 2012. I have office 2013 installed, win 8 64 bit. I get the above error for the below piece of code.
public void SetConnection(string text1, string text2, string text3, string text4, string text5, string text6, string text7)
{
connectionString1 = "Initial Catalog=test; Data Source=work\\sqlexpress";
connectionString = "Data Source='c:\\Users\\test1.xlsx';Extended Properties=Excel 12.0 Xml;Readonly=False;";
database = new OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;" + connectionString);
database.Open();
database1 = new OleDbConnection("Provider=SQLOLEDB.1;" + connectionString1);
database1.Open();
}
I tried using jet drivers but would not work, so i turned to ace. First i got "Cannot find installable ISAM"; so installed AccessDatabaseEngine_x64 which leads me to this error. I then changed my build to x86 and same errors. So i'm out of options. I did try previous versions of AccessDatabaseEngine from 2007 and 2010 but no luck, any suggestions.

database = new OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source='c:\\Users\\test.xls';Extended Properties= \"Excel 8.0;HDR=Yes;IMEX=1\";");
The above connection string works using jet although i have to leave the excel file open for the time being as i get "could not decrypt file" error otherwise. I also had to save the file as a 97-03 excel xls file.

string connectionString = "Provider=Microsoft.Jet.OleDb.4.0;Extended Properties=Excel 12.0 Xml;HDR=YES; Data Source=C:\Users\q\Desktop\Ug\Test.xlsx";

As said here, probably you have the 64-bit office installed which doesn't have the 32-bit compnents installed (links are provided there). You may also have to biuld your project targetint x86 platform.

How to open connection with Microsoft Access database in C#

I'm using Microsoft Access to create my database. Here's my code:
static string Constr = "Provider=Microsoft.Jet.OLEDB.4.0;"
+ "Data Source = MyData.accdb";
OleDbConnection Conn = new OleDbConnection(Constr);
DataSet DataSet1 = new DataSet();
string SQLstr = "Select * from Tabel";
OleDbDataAdapter DataAdapter1;
Conn.Open();
I'm getting this exception:
An unhandled exception of type 'System.Data.OleDb.OleDbException' occurred in System.Data.dll
Additional information: Unrecognized database format

You are trying to open an Access database created with Access 2007/2010 (accdb) with an OleDb provider that can understand only MDB files created with Access 2003
The provider to use is Microsoft.ACE.OleDB.12.0 that should be already installed with the latest version of Office.
In alternative you could download the appropriate bits from the Microsoft Access Database Engine
Just pay attention to download the version appropriate for the platform (x86 or x64) you use.
And that's the connection string to use
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=MyData.accdb";
NOTE: Keep in mind that if you have Office installed, the corresponding provider has the same bitness of Office, so with Office 64bit comes the ACE in 64bit version and the same for 32bit. This scenario poses a very difficult problem in deployment of your application. You need to have you application compiled with the same bitness or you will not be able to use the provider installed. (Or disinstall the incompatible Office version and reinstall the compatible one. Of course if you should be able to persuade your customer that Office is the incompatible app :-)

How do I connect to different versions of Excel from C#?

I have a program that imports data from Excel into a dataset. To connect to Excel I use the following code...
return new OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;" + "Data Source=" +
fileName + "; Jet OLEDB:Engine Type=5;"+ "Extended Properties=\"Excel 8.0;\"");
I just got a new computer with Excel 2010 and now the connection attempt fails and throws an exception saying The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
Is this because the new version of Excel needs a different connection string? Has anyone run into this?
EDIT:
Actually I just read somewhere that using the System.Data.OleDbClient class does not require Excel to even be installed on the computer. So my problem probably has nothing to do with Excel but rather with the Microsoft.Jet tool. My computer is running Windows7 64 bit. Shouldn't that be installed already?

Check out the Microsoft Access Database Engine 2010 Redistributable.
Redistributables for other Excel versions also exist.

You need to compile your program specifically for 32-bit so it will run in the WoW subsystem and invoke the 32-bit Jet provider. As mentioned above, there is no 64-bit version of the Jet provider and likely never will be.
In Visual Studio, you do this by setting your target CPU type in the project settings to x86 instead of Any or 64-bit.
If you don't have the source for your program, you can modify the .exe using the corflags.exe utility that comes with the .NET framework and the /32bit+ flag, but if it's a strongly signed assembly you'll need the .SNK to re-sign it once you've modified it.
Here is a reference on WoW64 if you need more detail: http://en.wikipedia.org/wiki/WoW64

I find this site useful when having connection string questions.
http://www.connectionstrings.com/excel
Also take a look at a previous SO question:
Diagnosing an OLEDB exception when Quering Excel 2010