<TITLE>ComponentSource</TITLE> <BODY BGCOLOR="White"> <CENTER><IMG SRC="../weblogo1.gif" ALT="[ComponentSource Logo]"></CENTER> <HR SIZE=2>

VB CodeReview

Quality Assurance for Serious Developers

VB/CodeReview will find all known bugs in your projects - so what are you waiting for ? You need this - go and get VB/Code/Review right now.

VB/CodeReview features :

Custom Control Bugs (OCX, VBX, DLLs, including usage and portability issues)
Visual Basic Bugs (Covers runtime and design time issues, including VB3 & VB4)
Data Access Bugs (Data Control, Bound Controls, DAO, Jet, ODBC)
Windows API Bugs (Win 3.x, NT, 95)
3rd Party Bugs (Popular 3rd Party Controls)

VB/CodeReview knows all about these and other common and fatal conditions:

Logic Errors (Recursion, type mismatches, loops and more)
Portability Issues (Conditions limiting projects to certain VB or Windows versions)
Performance (Common mistakes & conditions that reduce execution speed)
Standards (Spots non-compliant naming and user interface objects)
Usability (Duplicate accelerator keys, missing accelerators, missing help, mnemonics)
Guffaws (Ends, Stops, Resumes and other common and fatal mistakes)

Marquis VB/CodeReview scans projects for many conditions. The Marquis VB/CodeReview BugBase comprises over 2 megabytes of known bugs, performance zappers, and gotchas. Each file is read line-by line, and each line is reviewed for a match with any conditions in the BugBase.

Marquis VB/CodeReview NameBase, Marquis VB/CodeReview also scans the selected files for any non-standard naming. Marquis VB/CodeReview uses the NameBase, which is shared by other utilities as well. The NameBase consists of the files CLASSNAM.NDX and CLASSNAM.DBF. CLASSNAM.NDX contains all known Visual Basic object class names. CLASSNAM.DBF contains the actual prefixes to use. These two files work together to provide a consistant, manageable database of class names and standard prefixes. The NameBase is stored in dBASE III+ file format, not as MS Jet. The database engine used is Visual/db, also from Marquis Computing, Inc. Visual/db can index over 200 records per-second, offers memory based (buffered) file storage, and runs in the applications process making it many, many times faster than equivalent Jet calls. Also, Visual/db only requires about 75K of overhead vs several megabytes for MS Jet.