The best thing you can do is stick with Office/Access x32. The good news is there is no issue copying Access database objects between databases of different bitnesses, but the above listed exceptions still apply so you need to review the VBA code, ActiveX controls. Copying Objects Between Projects of Different Bitnesses
So you could in fact install MS Access 2010 圆4 along side of MS Access 2013 x32. What is possible however is to install different version with different bitnesses. In the case of MS Access, this applies to both Access and Access Runtime.
In other words you can not install a 32 bit version of word 2010, and a 64 bit version of access 2010 or Excel 2010 on the same machine.” - Albert Kallal, see: 32bit Access vs 64bit Access, Office 2010
“ many parts of office such as a spell checker, VBA code editor, and ribbon etc are shared components, the windows installing system and the office installer will NOT allow you to install mixed versions of ANY part of the SAME edition of office. The short answer is this is simply not possible. So if you deploy the Access 圆4 runtime on a machine with any previous version of office, you not be able to automate Word, Excel, Outlook etc.” - Albert Kallal, see: Anyone have EXPERIENCE in converting 32 bit Access to 64 bit? Installing Both x32 and 圆4 Versions of Office on the Same Computer In other words, you cannot mix and max the “bit size” of applications. “圆4 of Access cannot automate say Outlook 2007 or ANY previous version of Word. Yet one more reason never to use ActiveX controls in the first place!!! Office Automation Headaches “ ActiveX controls and COM add-ins that were written for 32-bit Office won’t work in a 64-bit process”Īnd what is worse is the fact that in many cases, it is not possible to find the 圆4 version of x32 ActiveX Controls. Private Declare Function apiGetUserName Lib "advapi32.dll" Alias _Īnd you must do this for all your APIs. "GetUserNameA" (ByVal lpBuffer As String, nSize As Long) As Long Private Declare PtrSafe Function apiGetUserName Lib "advapi32.dll" Alias _ 'x32 Declaration Private Declare Function apiGetUserName Lib "advapi32.dll" Alias _ "GetUserNameA" ( ByVal lpBuffer As String, nSize As Long) As Long #If VBA7 And Win64 Then '圆4 Declarations Private Declare PtrSafe Function apiGetUserName Lib "advapi32.dll" Alias _ I briefly explain how this is done in my article VBA – Early Binding and Late Binding – Part 2 and provide an example for the well known fOSUserName() function used to determine the current user’s login username. You will need to review all of you API calls providing conditional compilation directives containing modified API declaration that are compatible with both x32 and 圆4.
Microsoft themselves recommend installing the 32 bit version. Now some people erroneously believe that since their machine is running a 64 bit version of Windows that Office is automatically 64 bit as well, or that they must install the 64 bit version. A more and more common question in Access, and Office forums in general, relates to using Access x32 (32 bit) vs using Access 圆4 (64 bit).