Sample
Interface Sample Output On-line
Ordering Download Demo Flyer |
| When using Polisher, you have a great deal of control over the
polishing process. Below are detailed descriptions of many of the options available. |
General Formatting
Polisher can add 'Option Explicit' to require variable declarations, and align
declarations as clauses in one column. It can split multiple variable and 'Const'
declarations, multi-statement lines, and single-line If statements, and
split variables from code (e.g., numError: Resume Next). It
can also automatically remove optional variable names from the Next
statement, and manipulate line continuations in those dialects which support them. |
Return to previous topic or to the top of this page |
Spell Checker
The Polisher can check the spelling of standalone and embedded comments,
and/or text in the form definition found in properties such as 'Caption',
'Text', and quoted literals. The user can instruct the spell checker to ignore words
with all caps, words containing numbers, and Visual Basic key words. A
custom dictionary can also be created. |
Return to previous page
& topic or to the top of this page |
Code Line Indentations
Polisher can indent all of the code, none of the code, only the declarations, or only the
baselines. It can indent Case statements either 1 or 1/2 level to the right
of the 'S' in Select Case, or align the 'C' in the Case statement with the
'S' in Select Case. It can align the 'E' in the Else statement with the 'I'
in the If statement, or indent Else statements one half level to the right of the 'I' in
the If statement. The size of indentations is user-defined. |
Return to previous page & topic or to the top
of this page |
Conversion
Polisher can do a number of code conversion techniques to ensure that your
code stays up-to-date and runs well. It can convert DAO 2.x database references to DAO
3.x, as well as insert intrinsic constants. In addition, it can convert Global to Public and Dim to Private in the General
Declarations section of any file. |
Return to previous page & topic or to the top
of this page |
White Space
Blank lines can be ignored, removed, or automatically inserted before or after the
beginning or end of control structures. A user defined number of consecutive blank lines
can be removed as well. |
Return to previous page & topic or to the top
of this page |
Comment Formatting
Stand-alone and in-line comments can be left intact, removed, or automatically indented to
a specified column. In-line comments can also be automatically indented to the
indent level of the next or prior
line. |
Return to previous page & topic or to the top
of this page |
Comment Block
Different comment blocks can be inserted at the Module Level, for User-Defined Procedures,
and for Event Procedures. The Polisher can position comment blocks before
or after the start of procedures. Prototype comment blocks may have fixed
and variable text. The latter is provided by substitution variables and user input. |
Return to previous page & topic or to the top
of this page |
Debugging
To aid in debugging and maintainability of your code, Polisher can insert
line numbers by module, procedure or project. (Existing line numbers replaced); insert
error trapping code; insert proc entry/exit code; and identify untyped functions. |
Return to previous page & topic or to the top
of this page |
Y2K Checking
Analyzes code for Y2K (Year 2000) problems. All code is checked for date functions
(Day, Month, SerialDate, etc.) and data names that include the word date (StartDate,
EndDate, PayDate - but not Update). |
Return to previous page & topic or to the top
of this page |
Sample Interface On-line
Ordering Sample Output Download Demo Flyer |