The following VBA Declare statement example is modified to include the PtrSafe qualifier but still use a 32-bit return value: Declare PtrSafe Function GetActiveWindow Lib "user32" () As Long But because the return value has not been updated to a 64-bit data type, the return value is truncated, resulting in an incorrect value returned.įollowing is an unmodified legacy VBA Declare statement example: Declare Function GetActiveWindow Lib "user32" () As Long
The PtrSafe qualifier tells the compiler that the Declare statement is targeting 64-bits, so the statement executes without error. On 64-bit Office, this is incorrect because the pointer needs to be 64-bits. The modified VBA example contains the PtrSafe qualifier, but notice that the return value (a pointer to the active window) returns a Long data type. Running the unmodified Declare statement in 64-bit versions of Office will result in an error indicating that the Declare statement does not include the PtrSafe qualifier. To ensure backwards compatibility in VBA7 and earlier use the following construct: #If VBA7 ThenĬonsider the following Declare statement examples. Declare statements that include PtrSafe work correctly in the VBA7 development environment on both 32-bit and 64-bit platforms. The PtrSafe keyword asserts that a Declare statement is safe to run in 64-bit versions of Office.ĭeclare statements with the PtrSafe keyword is the recommended syntax. Implicit conversions of LongLong to smaller integrals are not allowed. Conversion functions must be used to explicitly assign LongLong (including LongPtr on 64-bit platforms) to smaller integral types. The LongLong data type is a signed 64-bit integer that is only available on 64-bit versions of Office. The actual data type that LongPtr resolves to depends on the version of Office that it is running in LongPtr resolves to Long in 32-bit versions of Office, and LongPtr resolves to LongLong in 64-bit versions of Office. VBA now includes the variable type alias LongPtr. Three important additions are the LongPtr type alias, the LongLong data type, and the PtrSafe keyword. The table at the bottom of this document summarizes the new VBA language features. To address this problem and enable VBA code to work correctly in both 32-bit and 64-bit environments, several language features have been added to VBA. This can result in memory overruns, unexpected results in your code, and possible application failure. The problem with running legacy VBA code in 64-bit Office is that trying to load 64-bits into a 32-bit data type truncates the 64-bit quantity. You only need to modify VBA code if it runs in the 64-bit version of Microsoft Office.
0 kommentar(er)
