InstantForum.NET v4.1.4StrataFrame Forumhttp://forum.strataframe.net/forum@strataframe.netTue, 07 Oct 2008 09:24:47 GMT20http://forum.strataframe.net/Topic15108-6-1.aspxThe steps for solving the issue applies to Windows XP Professional X64 too. ;)Mon, 19 May 2008 16:52:40 GMTGuillermo Vilashttp://forum.strataframe.net/Topic15108-6-1.aspxThat's very good to know about the 32-bit version of the Access connector. Thanks.</P><P>We ran into the same issues with the VFPOLEDB driver as well. However, since it runs several pieces through separate processes, we haven't been able to use VFPOLEDB at all on a 64-bit machine.Mon, 24 Mar 2008 08:38:18 GMTBen Chasehttp://forum.strataframe.net/Topic15108-6-1.aspxJust an FYI...<br><br>Developing on Vista x64 and trying to establish a connection to an Access 2007 database generated this error:<br>The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.<br><br>Access 2007 Connection String:<br>Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\myFolder\myAccess2007file.accdb;Persist Security Info=False;<br>Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\myFolder\myAccess2007file.accdb;Jet OLEDB:database Password=MyDbPassword;<br><br>The Access 2007 Database Engine currently only has 32-bit support.<br><br>For a .NET assembly built for "Any CPU" (the default platform setting in<br>build configuration), when it's run on x64 system, the JIT compiler will<br>compile it as 64-bit process; and we cannot load the 32-bit provider<br>(driver) in a 64-bit process.<br><br>The workaround is that you have to compile your assembly as a 32-bit<br>process specificially:<br><br>1) in VS2005, menu "Build/Configuration Manager"<br>2) in the "Configuration Manager" dialog, select "<New...>"<br>3) in the "New Solution Platform" dialog, select "x86", press OK<br><br>Also, there does not appear any plans to create a x64bit version.<br>Sat, 22 Mar 2008 14:29:16 GMTCrones