ACCESS RUNTIME 2010 FOR 64 BIT COMPUTERS 32 BIT
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. 圆4 accde must be compiled and run on Access/Office 圆4.x32 accde must be compiled and run on Access/Office x32.Decompile the original database and migrate it to the other bitness and then recompile itĬompiled versions (accde file format) must be compiled on the same version of the application they will be run on.Create a new blank database in the target bitness and import everything.When the General Rule Goes AwryĪlthough, a database made on Access x32 should run fine on Access 圆4 (and vice versa), some people report issues. Nevertheless, more and more people are using 64 bit versions of Office and Access and questions about compatibility abound, so I thought I’d try to explain some of the basics in plain English and try to centralize little bits of information scattered here and there into one simple to digest article.Īs a general rule, a database (in accdb file format) developed on Access x32 should run fine on Access 圆4 and vice versa. Personally, I see no benefit to installing the 64 bit version of Office/Access beyond Excel and Word being able to handle more data, but if you are requiring that to begin with, Excel/Word are the wrong tools! (but that’s entirely another discussion altogether).
“ We recommend the 32-bit version of Office for most users, because it’s more compatible with most other applications, especially third-party add-ins.” - Microsoft, see: 64-bit editions of Office 2013
Microsoft themselves recommend installing the 32 bit version.
ACCESS RUNTIME 2010 FOR 64 BIT COMPUTERS INSTALL
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).
0 kommentar(er)
