If you use the Microsoft OLE DB Provider for Jet or the Jet ODBC driver to connect to a data source in a 64-bit environment, you experience different problems. For example, you have a 32-bit application that uses the Microsoft OLE DB Provider for Jet. On the Provider page, select Microsoft Jet 4.0 OLE DB Provider. Enter the connection details for the Microsoft Access database: Click the Connection tab to display the Connection page. Apr 07, 2008 The MSDASQL provider only bridges OLE DB to ODBC. It does not bridge 64-bit to 32-bit. This means that 32-bit OLE DB Providers, such as Jet, and 32-bit ODBC Drivers, such as the text driver, are still inaccessible to SQL Server 64-bit.
Hi, i need to map the excel file with my dataset in asp.net application. I use New System.Data.OleDb.OleDbConnection('Provider=Microsoft.jet.OLEDB.12.0;Data Source=' & txtFilePath.Text & ';Extended Properties='Excel 12.0;HDR=YES;IMEX=1'), it works fine on my local (32 bit machine ) but not on server(64 bit). Also one thing i noticed on my system registry files, ther is jet folder inside in HkeyLOCALMACHINE /software/microsoft, BUT IT is not present on server. There may be the problem due to this,Please Suggest me how i can install these Jet Driver on my server machine(window server 2008 standard)(64 bit), which may help to solve my actual problem. But msjet40.dll are present on c:/windows/syswow/ but not on c:/windows/sys32 in server.
Also i have also used the link to download the setup,bt not getting solution. Rishi URL=miniclip/URL, URL=btjunkie/URL, URL=games/URL. Hi Rishi90, I assume the platform of the application targets anycpu. This issue occurs because. Microsoft doesn't provide a 64 bit version of the Microsoft OLE DB Provider for Jet and when a 64-bit application connect to datbase by using jet driver, it failed.
That's why you can find the msjet40.dll in the Windows SysWOW64 folder and can't find the registry. The 32bit registry on 64 bit platform is in the Wow6432Node. You can find the jet registry key in HKEYLOCALMACHINE SOFTWARE Wow6432Node Microsoft.
Microsoft Jet Ole Db Provider For Odbc Driver For Mac
To solve this issue, you can use one of the following solutions. One, change the target platform to x84, then application will always run as 32-bit application. Two, use the instead. Note, If you are an application developer using OLEDB, set the Provider argument of the ConnectionString property to “Microsoft.ACE.OLEDB.12.0”. If you are connecting to Microsoft Office Excel data, add the appropriate Extended Properties of the OLEDB connection string based on the Excel file type: File Type (extension) Extended Properties - Excel 97-2003 Workbook (.xls) 'Excel 8.0' Excel 2007 Workbook (.xlsx) 'Excel 12.0 Xml' Excel 2007 Macro-enabled workbook (.xlsm) 'Excel 12.0 Macro' Excel 2007 Non-XML binary workbook (.xlsb) 'Excel 12.0' If there is anything unclear, please let me know. Best Regards, Bob Wu MSFT MSDN Community Support.