Install visual basic for applications excel 2010

For example, after this patch is installed the version of vbe. If the directory is present you also have VBA version 6 installed.

Right click on vbe6. For example, after this patch is installed the version of vbe6. To download and install this patch: Click the Download link to start the download, or choose a different language from the drop-down list and click Go. Do one of the following: To start the installation immediately, click Open or Run this program from its current location. To copy the download to your computer for installation at a later time, click Save or Save this program to disk.

Running this installer once will patch both VBA5 vbe. Report abuse. Details required :. Cancel Submit. I had to deal with a similar issue some time back. Try to do a repair on MS Office. Highlight Microsoft Office.

Select Change and you should see the option to Repair. After it completes, restart the computer and try again. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site.

Palcouk Volunteer Moderator. All Declare statements must now include the PtrSafe keyword when running in bit versions of Office. It is important to understand that simply adding the PtrSafe keyword to a Declare statement only signifies that the Declare statement explicitly targets bits.

All data types within the statement that need to store bits including return values and parameters must still be modified to hold bit quantities.

Declare statements with the PtrSafe keyword is the recommended syntax. Declare statements that include PtrSafe work correctly in the VBA7 development environment on both bit and bit platforms. Consider the following Declare statement examples. Running the unmodified Declare statement in bit versions of Office will result in an error indicating that the Declare statement does not include the PtrSafe qualifier. 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.

On bit Office, this is incorrect because the pointer needs to be bits. The PtrSafe qualifier tells the compiler that the Declare statement is targeting bits, so the statement executes without error. But because the return value has not been updated to a bit data type, the return value is truncated, resulting in an incorrect value returned.

The following VBA Declare statement example is modified to include the PtrSafe qualifier but still use a bit return value:. To reiterate, you must modify the Declare statement to include the PtrSafe qualifier, and you must update any variables within the statement that need to hold bit quantities so that the variables use bit data types.

Following is a VBA Declare statement example that is modified to include the PtrSafe keyword and is updated to use the proper bit LongPtr data type:. In summary, for code to work in bit versions of Office, you need to locate and modify all existing Declare statements to use the PtrSafe qualifier.

You also need to locate and modify all data types within these Declare statements that reference handles or pointers to use the new bit compatible LongPtr type alias, and types that need to hold bit integrals with the new LongLong data type. Additionally, you must update any user defined types UDTs that contain pointers or handles and bit integrals to use bit data types, and verify that all variable assignments are correct to prevent type mismatch errors.

To write code that can port between both bit and bit versions of Office, you only need to use the new LongPtr type alias instead of Long or LongLong for all pointers and handle values.

The LongPtr type alias will resolve to the correct Long or LongLong data type depending on which version of Office is running. Note that if you require different logic to execute, for example, you need to manipulate bit values in large Excel projects, you can use the Win64 conditional compilation constant as shown in the following section.

To write code that can work in both new and older versions of Office, you can use a combination of the new VBA7 and Win64 conditional Compiler constants. The Vba7 conditional compiler constant is used to determine if code is running in version 7 of the VB editor the VBA version that ships in Office The Win64 conditional compiler constant is used to determine which version bit or bit of Office is running. The following table summarizes the new VBA language additions and provides an explanation of each.

Have questions or feedback about Office VBA or this documentation?