microsoft visual basic for applications 2013

What that article does not mention though is that Microsoft has provided declarations for the most commonly used API declarations that work in both 32-bit and 64-bit VBA. Without PtrSafe, the Declares will not execute in 64-bit Office. Still, it means you have to add PtrSafe to all your Declares, the idea being that you check that they work. In fact it does nothing at all other than to say to the compiler that the Declare works in 64-bit Office, whether or not it really does. The name of this attribute is dubious in that it does nothing to ensure pointer safety.

Some existing Declare statements will work fine on both platforms, but Microsoft chose to force developers to review all of them by introducing a new PtrSafe attribute. One implication though is that code written for 32-bit VBA may need revising to work in 64-bit Office, and I ran into this recently with some VBA code of my own. Visual Basic makes it easy to call the Windows API though the Declare statement.

It is based on the same runtime that powers Visual Basic 6.0, the last version before the.

The version is Office 2010 is 7.0.Īlthough it is embedded in Office, VBA is a powerful tool and there is not much that you cannot do. In fact, Visual Basic for Applications (VBA) has been slightly updated, and reports itself as version 7.1 in the preview. The first macro programming language in Microsoft Office was Basic, and it is still there in the forthcoming Office 2013.

Microsoft visual basic for applications 2013