We have an application that uses OLEDB and the Jet.Jet.OLEDB.4.0 engine. We convert our application, and also run it in 64-bit mode. However, the database engine is no longer a standard part of 64-bit Windows. But Office 2010 64-bit installs the 64-bit access database engine (see http://www.microsoft.com/downloads/en/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en ) so you can use Microsoft.ACE.OLEDB. 12.0
So, I'm working on troubleshooting, so our application also works in 64-bit mode. But the OLEDB code complains that the database engine is not registered. Therefore, I am trying to install a redistributable 64-bit engine at the above link. But he tells me that I need to remove the 32-bit Office 2007 first. I'm not going to do this because I'm sure some settings, etc. Will be lost.
So my questions are: How do 32-bit database access components not work in 64-bit mode, but you cannot install 64-bit if 32-bit is already installed? Does that really matter to anyone ?!
I understand that Microsoft wants people to switch to SQL Server Express, except that it is too invasive, installs reliably even on clean new computers running Windows 7, and does not just copy or move data between different machines. Is there a suitable alternative to Jet? Something simple, but works on 32 and 64 bits and perfectly supports OLEDB and ODBC? SQLite looks promising maybe?
source
share