Description

Shave weeks off your development projects by using this ready-to-run code. Every major area of software development is covered, from ADO to XML, with 90,000+ lines of code, 160+ modules and 40+ categories!

For a complete list of every class, module, and procedure, along with complete documentation, visit List of All Code. Of course, no code library is complete without thorough and comprehensive documentation. The code is documented with:

• Comments in the code itself
• Online help with syntax definitions and examples of every procedure!
• Industry-standard naming conventions
• Printed user manuals

What's New in This Version

• Supports Visual Basic 6 and all Office 2000 and Office XP applications.
• Access 2002 adds several new developer features that are accessible through code. Total Visual SourceBook now contains example code to work with the new functionality in Access 2002.
• New code is included for Active Server Pages developers, along with new JavaScript content.
• Includes code and examples for working with Active Server Pages (ASP) technology available in Microsoft Internet Information Server (IIS) versions 4 and 5.

Features

Code Explorer

Code Explorer is the user interface for Total Visual SourceBook and organizes all the source code. Use the Code Explorer to find the code you need, export it to your application, and manage your own code.

This is where you do most of your work. Code Explorer is used to find Total Visual SourceBook's own procedures as well as to create, copy, and edit your own procedures. The Code Explorer interface is divided into three main areas:

• The Treeview Window shows all topics, categories, classes, modules, and individual procedures.
   
• The Information Window shows detailed information about the current item selected in the Treeview. Details include the code, notes, and example code.
   
• The Tracking Window at the bottom shows Search Results and all the Bookmarks you defined.

Dual Modes
Code Explorer can run in standalone mode when invoked from the Windows Start Menu, or can run in "integrated" mode when called from you development program's Integrated Development Environment.

Finding Code
Total Visual SourceBook includes a powerful search capability, making it fast and easy to find the code you need. Simply select Search from the menu, and you can search by a variety of criteria. Total Visual SourceBook displays search results directly in the Code Explorer in the Search Results pane at the bottom of the form. This makes it easy to navigate through search results without having to switch to another window. (Click the image to enlarge)

Code Explorer Window
 

Using Code
Once you have found the code you need, you can export it using a number of modes:

• Export directly to Visual Basic, Access 2000/XP, Excel 2000/XP, Word 2000/XP, Outlook 2000/XP, or any other supported IDE
• Export to the Windows clipboard
• Export to a file
• Export to a Source Code Exchange file

Manage Your Own Code
Tired of digging for code you know you've already written? Use the Total Visual SourceBook Repository to store, index, and manage all your code in a shared environment. Track author, creation and modification dates, comments, examples and more. You can add:

• Modules
• Classes
• Procedures
• Code Snippets
• Examples
• Documentation
• Security Settings

Additionally, Total Visual SourceBook automatically maintains administrative information with your code for modification and creation dates, and code author name.

You can add code to the Total Visual SourceBook repository in one of two ways:

• Select Add from the Code Explorer Menu, and type or paste code into the Add/Edit dialog.
   
• Import code into Total Visual SourceBook directly from Visual Basic, Microsoft Access, or any of the other supported Integrated Development Environments.

The FMS Rich Text Editor

When you add your own code to Total Visual SourceBook, you can supply notes to describe it. Your notes can be plain text, or you can use Rich Text to add fonts, colors, bold face, italics, paragraph alignment, indentations, tabs, bullet points, etc. You can even add graphics, "live" hyperlinks, and OLE objects. 

The built-in FMS Rich Text Editor gives you these features and works like other text editors such as WordPad or Microsoft Word. As such, we do not go into a great detail on each feature of the editor or how to use a word processor. Instead, the main functions of the editor are described as they are listed on the menus. 

Source Code Exchange 
Our Source Code Exchange (SCE) technology allows you to share code when you aren't connected to your network. Take any code from SourceBook and package it into an SCE file--code, comments, and author information are automatically included. Then email your SCE file or put it on your website. Other SourceBook users can import SCE files and handle new and modified code with ease.

Here are some benefits to using SCE:

• Ideal for working in disconnected environments - Although Total Visual SourceBook provides seamless code sharing for your entire team, there are situations where you or other developers may not have access to the same shared drive. In this case, you can simply package your latest codebase as an SCE file and distribute it to remote team members. Before you know it, everyone is in sync.
   

• Supports code synchronization - When you import and SCE file into Total Visual SourceBook, the program scans the contents and compares it against the code already in your database. To handle conflicts with existing code, you can choose to overwrite, skip, or create new for each module or class.
   

• SCE Files are compact and self-documenting - SCE files use XML and compression technology to remain as small as possible for distribution over the web or with email. Additionally, when you create an SCE file, you can specify author name and contact information, notes, and copyright information.

Direct Integration with the Integrated Development Environment (IDE)
Total Visual SourceBook is completely integrated with the Visual Basic IDE available in Visual Basic 6, Office 2000, and Office XP. Start it as an add-in and its always ready to get you to the code you need!

Conventions and Style

All developers have their own style of writing code. In creating Total Visual SourceBook, we tried to take this into account. The style, comments, and error handling for each procedure are what we consider to be the best mixture of common practices, while allowing you to use and customize the code with the least disruption to your programming system.

Consistency
As we develop code for Total Visual SourceBook, we place a high premium on consistency in the style and techniques of the code in Total Visual SourceBook. After you use one procedure or class from Total Visual SourceBook, it should be very easy to find and use another one. There should be no arbitrary differences in naming conventions, commenting, and functional behavior. 

If several related procedures are included in a module, you can be sure that they always work similarly. Our assumptions and standards are described in this section, so you can easily convert from our standards to yours, if your situation requires it. For example, if you prefer a different variable naming convention to the one we use, it should be easy for you to translate our system to yours.

Error Handling
There are as many approaches for error handling as there are programmers. Each of us implements error handling in our own way because error handling logic is much more tied to the specific procedure than are naming conventions. Because of this, we tried to keep our error handling from getting in your way. We accomplish this by taking a minimalist approach to error handling-we don't want you to deal with complex error handling setup and maintenance every time you use the product's source code.

However, we strongly feel that every non-trivial subroutine, function, and property procedure should have a minimum level of error handling which accomplishes the following goals:

• Identify the name of the procedure with the error
• Display the error code and error message
• Prevent your program from crashing with a fatal run-time error

The following is the structure of the standard generic error handling style used in the code in Total Visual SourceBook:

Function GenericFunction() as Boolean
  ' Comments : Comments about GenericFunction
  ' Parameters: None
  ' Returns : True or False
  ' Source : Total Visual SourceBook
  '
  On Error GoTo PROC_ERR

  Debug.print 1 / 0

PROC_EXIT:
  Exit Function

PROC_ERR:
  MsgBox "Error: " & Err.Number & ". " & Err.Desc
  "GenericFunction"
  Resume PROC_EXIT

End Function 

Structured Programming Style and Formatting
The procedures, functions, and class methods used in Total Visual SourceBook follow the generally recognized standards for structured programming style. The following list includes the standards we use:

• Each subroutine or function has only a single exit point. "Exit Sub" and "Exit Function" are not used, except in the context of a single defined exit label.
   
• The "GoTo" statement is not used except to enable a module-level error handler. Similarly, the "GoSub" statement is not used. In rare cases, an unconditional branch to the procedure exit label may be used in order to avoid deeply-nested conditional code.
   
• Line labels are not used except for procedure handling exit points.
   
• There is no reliance on public or global variables for procedures. A class may have static shared data associated with it, but procedures and functions have no external data dependencies.

We use standardized formatting for items such as indenting, where local variables are declared, how in-code comments are formatted, and how error handling is enabled. While the standards may not match yours, we hope our consistent use of the same standards throughout the code make it easy for you to understand and use it.

Naming Conventions
Naming conventions are a touchy area for most developers. Opinions on the proper use of naming conventions vary much more widely than the consensus on other programming areas, such as the use of comments and structured programming style.

You may be among the developers who strongly believe that there should be no naming conventions at all. Or you may use a convention borrowed from the Microsoft-created "Hungarian" style directly from an entirely different language like C++. Some naming conventions are more idiomatic to the Basic language, such as using type declaration characters on variable names (Dim Name$ for example). Or you may be using a completely "non-standard" style that is dictated by the organization for which you develop.

As with many other areas of programming, the true value of using naming conventions may be the consistency they provide, rather than the merits of any one particular standard.

Total Visual SourceBook uses a consistent naming convention for the procedures and classes. The style selected is a variation on the recommendations that Microsoft makes in the "Visual Basic Coding Conventions" chapter of the VB Programmer's Guide. These include naming standards for controls, objects, menus, properties, types, constants, and other standard objects. The naming conventions also indicate scope, and whether or not the variable is part of an array or a collection.

Download Demos

Leverage your existing work by having your experienced developers store their custom code into the code repository for everyone to share. Eliminate repeated work, and get your junior developers up-to-speed faster without always bothering the senior developers. Follow the link below to download the demo.

Total Visual SourceBook for Access 2002/2000 and VB 6.0
 

Pricing
Total Visual Sourcebook - Single License		$395
Total Visual Sourcebook - 5 User License		$1295