E-mail Blog Facebook LinkedIn Twitter
User Testimonials

"I'm an avid supporter of MZ-Tools. It's a product I couldn't do without and your level of support is outstanding."

Jan Hyde (Visual Basic MVP)

"You will soon wonder how you ever lived without it."

Andy Maggs

"This is one of the most useful and best VB add-ins. Now that I have been using it I don't know how I ever worked without it. MZ-Tools has become my right hand in the VB IDE."

C. Kevin Provance

FAQ & Support of MZ-Tools 3.0 for Visual Basic 6.0, 5.0 and VBA

Is there a MZ-Tools version for Office 64-bit?

Office 64-bit does not support 32-bit COM (ActiveX) add-ins, only 64-bit COM add-ins, and MZ-Tools 3.0 is built with Visual Basic 6.0, which can only generate 32-bit components. Office 64-bit will be supported in the upcoming MZ-Tools 8.0 (expected for 2015).

I can't install MZ-Tools without admin rights, or I don't see it after installing it

When you install a VB6/VBA add-in dll, two things happen:

  • The DLL is registered as ActiveX (COM) component on the machine, using the HKEY_LOCAL_MACHINE registry entry. That means that to install MZ-Tools you need to be a member of the "Administrators" group.
  • The DLL is registered as add-in for some host, such as VB6 or the VBA editor, using the HKEY_CURRENT_USER registry entry. That means that MZ-Tools is installed only for the logged-in user, not for all users.

If you want to install MZ-Tools 3.0 for VBA for a non-admin user, you have two approaches:

  • Add the non-admin user to the "Administrators" group, log-on with that user, install MZ-Tools and remove that user from the "Administrators" group.
  • Make the admin user to install MZ-Tools (this step will register the dll as COM component on the machine for all users).

    With your non-admin user, search the "Windows PowerShell ISE" script editor of your Windows operating system and open it. Then, execute the following statements (this step will register the dll as add-in for the non-admin user):

    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

    New-Item -Path 'HKCU:\Software\Microsoft\VBA\VBE\6.0\AddIns\MZTools3VBA.Connect' -Force

    New-ItemProperty -Path 'HKCU:\Software\Microsoft\VBA\VBE\6.0\AddIns\MZTools3VBA.Connect' -Name Description -PropertyType String -Value 'MZ-Tools 3.0 VBA'

    New-ItemProperty -Path 'HKCU:\Software\Microsoft\VBA\VBE\6.0\AddIns\MZTools3VBA.Connect' -Name FriendlyName -PropertyType String -Value 'MZ-Tools 3.0 VBA'

    New-ItemProperty -Path 'HKCU:\Software\Microsoft\VBA\VBE\6.0\AddIns\MZTools3VBA.Connect' -Name LoadBehavior -PropertyType DWord -Value 3

If you "don't see" MZ-Tools after installing it successfully, it can be due to the following reasons:

  • MZ-Tools is not a standalone executable that you run from the "Start", "Programs" menu. MZ-Tools is an add-in (add-on, or plug-in) for an Integrated Development Environment (IDE) such as Visual Basic 6.0, Visual Basic 5.0 or the VBA editor of an Office application. The MZ-Tools setup configures MZ-Tools to load automatically in the IDE. You can check that MZ-Tools is installed in the IDE going to the "Add-Ins", "Add-in Manager" window. When MZ-Tools is loaded, it creates a new toolbar and a MZ-Tools menu under the main Tools menu.
  • The user who installed MZ-Tools and the user who is using MZ-Tools are not the same. See the explanations and workarounds above.
  • You have installed the wrong version of MZ-Tools. For example, you have downloaded and installed MZ-Tools 3.0 for VB6 (which uses the mztools3.dll file) while you are expecting it to appear in the VBA editor, which needs MZ-Tools 3.0 for VBA (mztools3vba.dll file).
  • You have installed MZ-Tools 3.0 for VBA and you expect to see it in an Office application, such as Access. However, MZ-Tools 3.0 for VBA is an add-in for the VBA editor of an Office application, not an add-in for an Office application. So, to see it, you have to open the VBA Editor (Alt+F11).
  • You have installed MZ-Tools 3.0 for VBA and you are using the VBA Editor of Office 64-bit, which is not supported (only 32-bit versions are supported).
Where are the MZ-Tools settings stored, so they may be backed up and restored?

The MZ-Tools settings are stored in the following locations:

  • The settings that you set in the Options window are stored in .ini files in the locations explained in the section Customizing MZ-Tools of the help file or online documentation.
  • Some personal settings such as your favorite procedures, favorite projects, windows sizes and other volatile information are stored in the same registry entry used by Visual Basic to locate add-ins, that is:

    - For Visual Basic 6.0: HKEY_CURRENT_USER\Software\Microsoft\Visual Basic\6.0\AddIns\MZTools3.Connect
    - For VBA: HKEY_CURRENT_USER\Software\Microsoft\VBA\VBE\6.0\AddIns\MZTools3VBA.Connect
    - For Visual Basic 5.0: HKEY_CURRENT_USER\Software\Microsoft\Visual Basic\5.0\AddIns\MZTools3VB5.Connect

    To backup registry settings, use the RegEdit.exe tool, select the desired registry node and click the File | Export... menu. The settings will be exported to a .reg file that you can restore later just by double-clicking on it or using the RegEdit.exe tool again.
I get an error with the clipboard when MZ-Tools is loaded

Due to the method implemented by Microsoft to use custom images in buttons of add-ins, MZ-Tools must use the clipboard during the load. If other application (such as a clipboard utility or a graphics application) is using or locking the clipboard, unload it. This problem can happen also with remote desktop utilities such as Remote Desktop, Terminal Server, etc.

The Visual Basic IDE menus have been corrupted

This can happen in two scenarios:

Anyway, to solve this problem:

  • Unload all add-ins.
  • Right-click on a toolbar and select the Customize... menu.
  • For each toolbar click the Reset... button (6 times in total).
  • Reload the add-ins.
MZ-Tools 3.0 for VB or VBA prompts to repair Visual Studio (.NET)

There can be several causes for this issue, such as:

  • You installed Visual Studio from a unit drive that is no longer present (such as from a USB hard disk). As a workaround, you can uninstall Visual Studio, copy the setup to the C:\ unit and reinstall it from there.
  • The "C:\Windows\Microsoft.NET\Framework\URTInstallPath_GAC" folder does not exist. As a workaround, you can create it.

Other than those, somehow some product of Visual Studio (.NET) thinks that some component is missing. See how to diagnose the issue in this post and all the comments.


Any problem not addressed here? Don't hesitate to ask.