|
|
|||
|
||||
|
||||
|
Will there be a version 4.0 of MZ-Tools for VB6/VB5/VBA? No, there are no plans to create new versions with new features or enhancements for VB6/VB5/VBA but MZ-Tools 3.0 will be supported through builds with bug fixes.
Will the source code of version 3.0 be released (as open-source or sold, for example)? No, the source code will not be made available as open-source and cannot be bought either. If you want a fix for a bug, report it and likely it will be fixed in the next monthly build. If you want the source code for learning purposes, the best way to learn is to develop your own add-in. You can post specific questions in the Microsoft newsgroups and likely you will get the answers.
I need a feature that is not provided by MZ-Tools (such as a code indenter) You can take a look at end of the Download page to see if other add-ins can provide the missing feature.
Is there a MZ-Tools version for Office 97? No, Office 97 does not support COM-Addins.
How do I apply some feature such as Line Numbering or Error Handlers to a whole file, project or project group? The current version does not support adding error handlers to a whole file, project or project group, because I think that error handling is so important that it should be an integral part of the procedure logic (not an afterthought) and therefore it should be done carefully, one procedure each time, and not in a massive or blind fashion. Other features such as Line Numbering or Reviews can be applied to a whole file, project or project group as it is explained in the help file for each feature, but here is the answer:
Where are the MZ-Tools settings stored, so they may be backed up and restored? You may want to backup the MZ-Tools settings for safety or you may want to share the settings between two computers (at home and at the office, for example). The MZ-Tools settings are stored in the following locations:
Some features of MZ-Tools for Visual Basic are not included in MZ-Tools for VBA. Why? This is explained in the "Using MZ-Tools" topic of the help file.
When I use the "Copy Control(s) With Code" feature with Access I get the error "There is no active designer". Why? That feature works with forms of Visual Basic, or VBA userforms of Word or Excel ("Insert", "UserForm" menu). On the one hand Access lacks VBA UserForms and on the other hand an add-in for the VBA editor of Access can not access the forms or reports of Access, because they belong to Access itself and MZ-Tools is not an add-in for Access but for its VBA editor.
When I add a button of MZ-Tools to another toolbar, the button does not work after restarting the IDE. Why? The VB or VBA IDEs don't support adding buttons from an add-in to another toolbar, that mechanism only works with built-in buttons of the IDE. When the add-in is reloaded, it is no longer associated with buttons that it does not create at that moment. Visual Studio .NET introduced the concept of (permanent) commands, from which you create buttons, and that mechanism works perfectly in that IDE, but not in the old VB / VBA IDEs.
I have problems installing MZ-Tools When you register a VB6/VBA add-in dll, two things happen:
If you receive the error code 0x80004005 when registering MZ-Tools, it can be caused by these known reasons:
If you want to install MZ-Tools for a non-admin user, you have two options:
I have problems loading MZ-Tools When MZ-Tools is loaded, it creates a new toolbar, a MZ-Tools menu under the main Tools menu, and some context menus in the Project Explorer. If MZ-Tools is not loaded after registering it successfully, it can be due to the following reasons:
MZ-Tools should be loaded without errors. The only known exceptions are the following:
I have problems unloading MZ-Tools or the Visual Basic IDE MZ-Tools should be unloaded without errors. The only known exception is a GPF that can occur if it is loaded another add-in that also does window subclassing with the main window of the VB IDE (just as MZ-Tools does). In this case, add-ins should be unloaded in reverse order to properly restore the subclassed window procedures. Unfortunately, VB unloads add-ins in the same order that they were loaded, not in reverse order. So, if you have two add-ins that are loaded on startup and both do subclassing, you will get a GPF when unloading VB. To solve this issue, you can use any of these ways:
The Visual Basic IDE menus have been corrupted This can happen in two scenarios:
Anyway, to solve this problem:
The shortcut created for a built-in VB feature (such as Comment Block) does not work. Why? If shortcuts for non built-in VB features (such as Add Procedure Header) work fine then it is not a problem with the shortcuts. Likely is because your Edit toolbar has been customized or is corrupted and does not have the button for the built-in VB feature, which MZ-Tools tries to use when invoking the shortcut. In this case, MZ-Tools fails silently. To solve this problem follow the procedure of the previous section to reset the toolbars and try again.
The Make Project Group menu of the Visual Basic IDE is disabled This can happen from time to time but it is not reproducible at will. MZ-Tools sets an event handler to it to capture click events for the reviews before making the executable, and maybe this causes some kind of interference. To solve this problem follow the procedure of the previous section to restore the menu state and download the build 3.00.1003 or higher. From this build MZ-Tools does not trap events of the Make Project Group menu so the problem should disappear. Unfortunately this means that the Reviews Before Making The Executable will not be executed when you use the Make Project Group menu, only when you use the Make Project menu.
There are problems with the images of the buttons of the MZ-Tools toolbar Some known problems are the following:
Any problem not addressed here? Don't hesitate to ask. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
 |
|
