#USE MS OFFICE 32BIT OR 64BIT? HOW TO#
#USE MS OFFICE 32BIT OR 64BIT? UPDATE#
#USE MS OFFICE 32BIT OR 64BIT? UPGRADE#

Theoretically you can avoid this last step by declaring them as variants, BUT: The ONLY way to deal with the PtrSafe requirement is to wrap declare statements in compiler conditionals to determine whether PtrSafe should be used.Дeclare PtrSafe Function FindWindow Lib вЂњuser32вЂќ Alias вЂњFindWindowAвЂќ (ByVal lpClassName As String, ByVal lpWindowName As String) As LongPtrДeclare Function FindWindow Lib вЂњuser32вЂќ Alias вЂњFindWindowAвЂќ (ByVal lpClassName As String, ByVal lpWindowName As String) As LongДЄny variable declarations or procedure declarations involving pointers should be similarly wrapped so that they can be declared as either Long or LongPtr. Secondly, if the application ever needs to work in 2007, the PtrSafe keyword AND the LongPtr data type are not recognised, causing compile errors! Firstly, updating the declare statement is great, but if youвЂ™ve been using good practice in your coding you will have multiple variables declared either locally or globally that either pass or receive Longs to declare statements, and these will all need to be updated to LongPtrs. In theory this is great, but there are 2 significant issues.

#USE MS OFFICE 32BIT OR 64BIT? UPDATE#

You are intended to update each declare statement with appropriate LongPtrs and then add the PtrSafe keyword to indicate that this statement is now 64-bit compliant.ДЄn example of one such compile error, when preparing 32-bit code for use in 64-bit Office The logic here is that without the PtrSafe keyword, any declare statements will cause a compile error on 64-bit, which highlights to the developer that there are issues with the code. In 64-bit, it is a MANDATORY keywordвЂ¦.that still has absolutely no effect! In 32-bit Office 2010 this is an optional keyword that has absolutely no effect. Since sending a DLL with the wrong size value can be a REALLY bad idea, Microsoft introduced a new keyword to the declaration statement called PtrSafe. API/DLL CallsДЄs I stated earlier, the LongPtr data type will most often be needed in API or DLL calls requiring pointers or handles (to windows, or processes, or code in memory, orвЂ¦.well A LOT OF STUFF). This is HIGHLY annoying because it means you cannot simply find/replace Long with LongPtr to вЂњupdateвЂќ code. One small catch with the LongPtr data type is that although it IS either a Long or a LongLong, because it is intended for pointers and handles only VBA will NOT ALLOW you to perform arithmetic functions on it (such as using it in a loop). This allows you to вЂњeasilyвЂќ write code that will work between both 32 and 64-bit Office installations (as long as they are both 2010+). At compile time this will BECOME a 64-bit number on Office 64-bit (LongLong) and a 32-bit number on Office 32-bit (Long).

Helpfully Microsoft has added a new data type in VBA 7 (Office 2010) called a LongPtr. Unfortunately previous versions of Office (2007 backwards) do not have a data type that holds a 64-bit value, and in 2010 32-bit, you donвЂ™t want one! Fortunately VBA uses VERY few pointers 95% of them are involved in API or DLL calls. The main difference between 32 and 64-bit Microsoft Office (VBA wise) is that any pointers now need to be 64-bit rather than 32. There are actually very few issues with moving code from 32-bit Office to 64-bit Office, but a couple of them are significant.

#USE MS OFFICE 32BIT OR 64BIT? HOW TO#

If you donвЂ™t care about reasons or explanations, skip to the summary to see how to avoid or fix the issues. ItвЂ™s the first time this has been an issue, and I thought IвЂ™d detail some of the effects.

#USE MS OFFICE 32BIT OR 64BIT? UPGRADE#

In the last week IвЂ™ve had a client upgrade to 64-bit Microsoft Office and it has caused some havoc with parts of my VBA.

Use ms office 32bit or 64bit?