VBA Coding Tools for Your Entire Enterprise
Integrated directly into the VB/VBA Integrated Development Environment, Total Visual CodeTools gives you a rich set of enterprise-enabled coding tools. Increase productivity and let your entire development team share a consistent set of standards and rules.

Code Cleanup
Taking over someone else's code is difficult enough without trying to read non-standard styles. Our Code Cleanup feature solves this problem by letting you standardize existing code at the procedure, module, or project level. Apply your naming conventions, comment styles, error handling and visual standards. You can add error handling to procedures that lack it, and even automatically update it as your project changes.

Code Delivery
Code Delivery preps your code for distribution. Add line numbers to every line so your error handler can pinpoint errors after your application ships. Drastically reduce the time and headaches spent reproducing bugs, or trying to decipher user bug reports. Code Delivery also removes all debug code and compresses code for faster execution in non-EXE environments such as Microsoft Office.

Code Builders
Code Builders are available to help you create new code quicker and with flawless conformance to your standards. All builders use the shared standards you define -- just point and click and new code is generated for many aspects of your application.

Coding Tools
Total Visual SourceBook also includes a set of coding tools to handle the more mundane tasks of working with VB and VBA.

Enterprise Enabled Standards Management
Total Visual CodeTools allows you to define all aspects of your coding standards, including visual style, indentation, error handling, commenting, variable naming conventions, and more. Define your settings once, save them to a shared location, and your entire team can use your enterprise standards without even thinking about it.

Features

Multi-product support
Support for programmers in any VB/VBA editor environment. In addition to Access 2000, Total Visual CodeTools 2000 supports VB 6.0, Office 2000/2002, and other VBA environments that support VB/VBA add-ins

VBA 6 support
Supports VB/VBA syntax of Visual Basic 6.0 and Access/Office 2000/2002

Enterprise Standards Management
A centralized set of standards across Builders, Code Cleanup, and Code Delivery that is saved to a file and shared among developers. This simplifies maintaining consistent standards across an entire development team.

Recordset Builder
Use the Recordset Builder to easily create ADO and DAO recordset objects.

Builder Enhancements
The Procedure and Property builders support customizable templates for comments (procedures vs. properties) and error handling (modules vs. classes) Long Text and SQL Builders combined into one builder.

Code Cleanup Enhancments
Code Cleanup previously modified all your code. In this version, you can choose to cleanup a procedure, module(s), or entire project. Different error enabler and error handler templates can be specified for regular modules vs. class modules. Previously, there was only one setting for both. Error enabler and error handler sections can be added with tags to allow automated updates in the future. Comment templates can be customized separately for procedures and properties.

Set the maximum number of consecutive blank lines Option to split single line IF..THEN.. statements into separate lines with an ENDIF. Variable renaming prefix for procedure parameters, arrays, and enum. Option to skip the renaming of variables that are in ALL CAPS.

Code Delivery Tool
Total Visual CodeTools has a new feature called Code Delivery. This tool creates a "delivered" version of your code by removing blank lines and indentations, renaming variables to short meaningless names, and removing comments. The result is a version of your code that is smaller, faster, and most important, more secure against de-compilation. It's especially useful in situations where you must deliver source code in an un-compiled state.

Code Delivery also adds line numbers to your code so your error handler can use the ERL function to determine the exact line where a crash occurs. Solutions are usually quite obvious if you know exactly where a crash occurs. This reduces the effort required to replicate bugs or consult with end-users. Many VB/VBA developers insist on using this feature before releasing any of their programs.