Total Visual CodeTools Frequently Asked Questions
What version of Total Visual CodeTools do
I need?
What versions of Access/Office/VB6 does it support?
-
Total Visual CodeTools 2010 is the latest version and supports the latest VBA/Visual Basic 6.0
environments:
- Visual Basic 6 (VB6)
- Office, Access,
Excel 2010 (32 bit), 2007, 2003, 2002 (XP), and 2000.
- Other VBA environments
-
For Access 97, Total Access CodeTools 97 is available.
- Support is not available for the 64-bit version of Office
2010
- By default, Office 2010 installs the 32-bit
edition. Most users are running the 32-bit version of
Office even if the operating system is 64 bit.
- Total Visual CodeTools 2010 support Office 2010
32-bit on 64-bit versions of Windows
Check the
Product Compatibility Chart for version information for all of our products.
Can I try Total Visual CodeTools before I buy it?
Yes. Download the
free
Trial Version to try Total
Visual CodeTools before you buy it.
Also, remember that FMS products come with a 30-day money
back guarantee, so you can
buy with confidence!
Total Visual CodeTools does not appear on my
Access Add-ins menu
Total Visual CodeTools does not appear on the add-ins menu/ribbon
in the main Access program.
Total Visual CodeTools is an add-in for your module editor.
It appears in the VBA module
editor. To use Total Visual CodeTools in Access, open any
module (or press Alt-F11) to open the VBA editor.
If Total Visual CodeTools is properly installed, it appears on the menu as
"Total Visual CodeTools".
Under the Total Visual CodeTools standards, you can
modify the location where it appears so that it can also
appear under the Add-ins or Tools menus.
If you still can't find the Total Visual CodeTools menu
item, it may be temporarily disabled. Look under Add-ins,
Add-in Manager to find "Total Visual CodeTools 2010" then
change the Load Behavior to Startup/Loaded. If it's not on
the list, it's not installed properly. You may need to
uninstall and reinstall it.
Total Visual CodeTools is missing from the VBA or
VB6 IDE Menu
When you install Total Visual CodeTools, the setup program creates
registry entries so the Microsoft Visual Basic 6 and Office programs can
integrate it into their add-ins menu.
Total Visual CodeTools installs as a “loaded” add-in. This means that
whenever you start Visual Basic or the Office Visual Basic Editor, the Total
Visual CodeTools menu item and toolbar are ready to go.
Because of Microsoft’s support for VBA/VB6 add-ins on a user rather than
machine basis, if you installed Total Visual CodeTools under a different
Windows login name, you’ll need to load it again.
For Visual Basic 6 (VB6)
For VB6, you can simply select it from the Add-ins Menu.
For VBA (Microsoft Office, Access, Excel, Word, etc.)
For VBA, you need to update the registry. Exit your VBA host program
before doing this. For your convenience, a REG file is included in the
installation directory of Total Visual CodeTools that you simply need
to run. Locate the file named VBA-Addin.reg, and double click it. A warning
may appear requesting administrator rights or other confirmation. Click [Yes] to confirm the registry change, and the registry is updated
for the current user. The registry file contains the following information:
Total Visual CodeTools 2010
[HKEY_CURRENT_USER\Software\Microsoft\VBA\VBE\6.0\Addins\TVCTLVBA.CAddInConnect]
"FriendlyName"="Total Visual CodeTools 2010"
"LoadBehavior"=dword:00000003
"Description"="Total Visual CodeTools 2010 from FMS, Inc. (www.fmsinc.com)"
"CommandLineSafe"=dword:00000000
Total Visual CodeTools 2007
[HKEY_CURRENT_USER\Software\Microsoft\VBA\VBE\6.0\Addins\FMSVBEI.CAddInConnect]
@=""
"FriendlyName"="Total Visual CodeTools"
"LoadBehavior"=dword:00000003
The next time you run your VBA host, Total Visual CodeTools appears
on the module editor menu.
I receive an error when I run Total Visual CodeTools
- Error 3021, "No current record"
- Error 40179, "Requested type library or wizard is not a VBA
project."
This issue can occur in an Access database that contains a corrupt object
(e.g. a module or code behind form or report). In many cases, such
corruption can be resolved by following the steps to
decompile
and recompile your database.
If you still encounter this error after following these steps,
please
contact us
so that we can be of further assistance.
Main Total
Visual CodeTools Page
