None |
VBA Support for 64-bit DPE Client |
VBA 32-bit application is supported with 32-bit version of DPE client. However, in Visual Studio 2008, Microsoft has stopped native support for 64-bit version of VBA. This section provides information on the the work-around being provided to this in DPE and its limitations
32-bit software is supported on Windows 64-bit platform as a 32-bit processes. It is executed inside the dedicated Windows on Windows’ (WOW64) subsystem that is part of all 64-bit Windows operating systems. Using Inter-process communication (IPC) technique, a 32-bit out-of-process COM component is now being used to support VBA with DPE 64-bit Client. A separate 32-bit process EPVBAProcess.exe is launched whenever any VBA functionality is invoked. That is, this would happen whenever - a VBA IDE is opened OR VBA Macro is executed OR VBA Macro is loaded into script command properties dialog.
This happens because the project items; example: Data,
Config, Dialog... that are used in 32-bit DPE client is now
different in 64-bit DPE client.
Limitation 2: Intellisense does not work correctly when you type something in VBA IDE and press Ctrl + Space bar.
Work Around: First press Ctrl + Space and then start typing the required function
Work Around: Use GetTypeInfoEx. All instances of GetTypeInfo while running on 64bit platform should be converted to GetTypeInfoEx.
Limitation 4: Such an architecture (IPC)
ensures the same level of functionality but may not ensure
the same level of performance. |
None |