-
Notifications
You must be signed in to change notification settings - Fork 24
Open
Description
I had trouble to identify the VBE7.dll to modify in order to make it works and I want to share an approach to help you find it.
The simplest way is to start an Office product (Excel, Access, ...) and open the Visual Basic Editor.
Then you can list the loaded modules and find which VBE7.dll is actually loaded.
Listing the modules can be done with ProcessExplorer or SystemInformer.

Or you can use a simple Powershell line to find it:
((Get-Process -Module -ErrorAction Ignore) | Where-Object { $_.ModuleName -eq "VBE7.dll" }).FileNameHowever, with this approach you have to be careful regarding the bitness of Powershell vs. Office vs. Windows.
On Windows 64-bit (x64), with Office 32-bit (x86), you'll need to start the Powershell 32-bit (x86) otherwise it will not list the 32-bit loaded modules.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels