Click the image to enlarge. More screen shots at the bottom of this page.

Download the shareware version 1.0.13: Vcs61.exe 1122KB
Alternate download version 1.0.11: Vcs61.exe
Place credit card order on-line: Credit Card Order
For cash, check, or money order orders select Order Form from the program's Help menu.
Problems, questions, or comments - send email to

Also try Code Base Alpha - the ultimate VB Add-In. Both programs are sold together for one low price.

 Scanning A Project

Visual Code Scan 6 was built to scan Visual Basic 6 projects for dead code, unused or undeclared variables, and functions with no return type or old style return declarations. It also extracts strings so they can be checked for spelling. All of the information can be viewed in reports or you can edit the code right in Visual Code Scan 6's own code editor.

A project can take anywhere from 2 minutes to an hour and a half or more to scan. On an AMD K6 II with 128 MB of RAM, a project with 25 project files and 10,000 lines of code will take a bout 4 minutes to scan. A project with 100 project files, and 30,000 lines of code will take about an hour and a half to scan.

 Edit The Code

Double-click on any routine name, variable, or constant to bring that code up in the code window. The code is colored just like the VB edititor with the addition that problem code is highlighted as well. From here you can edit the code and save your changes.

The code editor has the usual cut, copy, paste, and select all. It also comes with a Find utility, and Indent, Outdent, and Comment. The last three work with a block of selected text to either shift the block of code left or right, or comment out a block of code.

 Zip Up The Project

After you have opened and scanned a project you can chose to have Visual Code Scan 6 zip all project files before you begin to fix repairs. You also will have the option to zip up individual files prior to saving any changes you've made.

 Files and Routines

Project files are displayed in much the same way as they are in the Visual Basic Project Explorer. Each file has it's own list of statistics about the file including any DLLs, external objects, or references it relies on. When you click on a file a list of it's routines appears to the right. The routine's icon will indicate any problems the routine may have.

When you click on a routine name from the Routines list the three panes to the right of the Routine List will display information about that routine. The top pane displays any problems with the routine along with information about the routine. The middle pane lists any parameters passed into the routine. The bottom pane lists any routines called by the selected routine, and any routines it calls. You can double click on the routine, any of the parameters, Called by or It Calls routines to view that code in the code editor.

 Check Your Spelling

As the program parses the project files it also extracts every quoted string and every caption, text, and list property. It also goes inside FRX files to get ListBox and ComboBox Text assignments. All of this information is set in a ListView on the Spell Check tab.

From here you can review MsgBox calls and other string assignments for spelling errors. If you have Microsoft Word 97 or greater the program will use the Word 8 object library to run the Word spell checker on all of the strings. Any corrected text will appear in the far right column on the Spell Check tab and a check mark will appear next to that list item. Only those items with check marks will appear on the Spell Check report.


Visual Code Scan 6 gives you three reports. The reports are displayed in a window where they can be viewed, saved to disk, or printed.

The spelling report is available after you run the spell checker on the extracted strings. It will list only those items that have corrected text available. You will see the file, routine, and property or variable the text belongs to, along with the original text and the corrected text.

The code report lists all of the information available in the Code Review Window.

The statistics report lists all of the files and folders in the project, along with date, time and size of each file. It lists all of the dlls and objects, along with complete version and path information for each file. It lists the references made in the project.

For the code, the report lists the number of routines, lines of code, comment, and while space. It lists the longest, shortest, and average routine length. It also lists the number and types of variables, types, objects, and enums used.

 Screen Shots

Visual Basic News & Information Source