Dec 212017
 
Fine tune dBASE progs for quicker program runs.
File TUNE31PC.ZIP from The Programmer’s Corner in
Category Dbase Source Code
Fine tune dBASE progs for quicker program runs.
File Name File Size Zip Size Zip Type
DT31PC.DOC 9600 3679 deflated
DTUNEPC.COM 32256 19872 deflated

Download File TUNE31PC.ZIP Here

Contents of the DT31PC.DOC file


==== Documentation for dTUNE Version 3.1pc ====

dTUNE (C) Version 3.1pc
(IBM PC and Compatibles)
A Utility For Use With dBASEII(tm) Command Files
by James A. Gronek

dTUNE is Copyright (C) 1984, 1985
by
UCS, inc.
P.O. Box 23866
Phoenix, Arizona 85063

ALL RIGHTS RESERVED


==== Description ====

dTUNE is a utility program for use on dBASEII and dBASEIII
or III command files by removing all unnecessary spaces, tabs,
line feeds and comments. Further, it shortens reserved words and
phrases to their minimum four character length. Because dBASEII
parses every character of every line prior to executing it, dTUNE
will dramatically improve the running speed of almost any .PRG
file.

dTUNE has many additional features for the dBASEII and III
programmer, including the ability to uniformly alter the case of
the .PRG file, prepare a documentation quality file with nesting
and indenting, prepare a line numbered file and associated cross-
reference listing of variables, and other options described more
fully below. Your original source file will not be altered IN ANY
WAY.

==== Installing dTUNE ====

dTUNE has been pre-installed for an 80x25 b/w display and
should run on nearly any true blue or pclone under ms- or pc-dos.

==== Using dTUNE ====


dTUNE is executed with the command:

A>DTUNE

dTUNE will sign on, and ask you for the default directory.
This selection tells dTUNE where the command file to be processed
is located, and what drive to use for the output files. If, at
this point, you press the default directory will be the
one you were logged on when you called up dTUNE. When selecting
a new directory path it is imperative that you prefix your
directory selection with a backslash ("\"). Thus, if you call
the program up from the root directory on the "A" drive and wish
to process a .PRG file in the "B" drive under the "DBASE" subdir-
ectory, you would type "B:\DBASE". If you wish to process a .PRG
file on the CURRENT drive under the "DBASE" subdirectory you
would type "\DBASE". You may select any valid drive/path
combination.

Once you have selected the default directory, you will be
presented with a list of the .PRG files on that drive and
prompted for the FILENAME of the file to be processed. You need
only supply the PRIMARY filename, dTUNE assumes the .PRG
filetype.

Once dTUNE has verified the existance of the file to be
processed, you will be prompted for processing options. These
options are detailed, in the sequence presented, below:

OPTION 1: Cross-Referencing of Variables

dTUNE will ask if you wish a cross-reference listing of all
non-reserved words and variables. Acceptable answers are Y or N,
either upper or lower case. If you answer Yes to the prompt,
dTUNE will prepare TWO files from the source file. The first will
be a line numbered file with a filetype of .PRN, the second will
be a listing of all non-reserved words and variables, in
alphabetical order, showing the line numbers in which they
appear, saved with a filetype of .XRF.

dTUNE will handle in excess of 300 variables, if necessary,
but the use of so many variables is not recommended! dBASEII's
internal limitations specify a maximum of 64 variables, so you
can see that there is considerable latitude allowed by dTUNE.

---- NOTE - KNOWN LIMITATION ----

The cross-reference file (type .XRF) cannot be longer than
about 14K. dTUNE's internal memory limitations will cause it to
abort processing with a reported error code of 'FF', indicating a
Heap/Stack collision. If this occurs to you, simply break your
command file into two, or more, separate files, then process them
both. Unless your command file is over 2000 lines in length, AND
uses over 300 memory variables, this should not be a problem.

OPTION 2: Preparation of Structured Source

dTUNE will next ask if you wish a structured version of your
source file. Acceptable answers are Y or N, either upper or lower
case. If you answer Yes to the prompt, you will receive another
prompt, asking if you wish to alter the case of the source code.
Again, acceptable answers are Y or N, either upper or lower case.
If you answer No to this prompt, the case of your structured file
will be the same as the case of your source file.

If you answer Yes to the Case prompt, dTUNE will ask whether
it should make the structured file UPPER CASE or lower case.
Acceptable answers are U or L, either upper or lower case. dTUNE

will uniformly alter the case of the structured file, excepting
quoted strings. Strings may be delimited with either a single
quote mark ('), or a double quote mark ("). dTUNE will read
source files in UPPER CASE, lower case, and MiXeD CaSe with equal
ease.
-- NOTE --

dTUNE WILL NOT ALTER YOUR SOURCE FILE, IT CREATES A
TEMPORARY FILE FROM WHICH TO WORK, ENSURING THE INTEGRITY OF YOUR
ORIGINAL SOURCE FILE!!!

If you answered Yes to the Structured Source prompt, dTUNE
will save your structured file with a filetype of .TXT.

OPTION 3: Preparation of a Structured version
of the processed file

dTUNE always prepares a .PRG file that has no indentation,
nesting, or comments, and has all reserved words and phrases
shortened to the minimum four character length. The resultant
file is nearly impossible to understand. This option will prepare
a nested version of the processed file, allowing you to follow
the logic with more ease. This file may be substituted for the
unstructured .PRG file with negligible difference in running
speed.

You will be asked if you wish a Structured version of the
Processed file. Acceptable answers are Y or N, either upper or
lower case. If you answer Yes, dTUNE will save the structured
version of the processed file with a filetype of .STR.

OPTION 4: Listing of Structured version of Source

You will be asked if you wish a Structured Listing of the
Source code. Acceptable answers are Y or N, either upper or lower
case. If you answer Yes, dTUNE will print a structured version of
your source code to the LST: device (normally the printer).

Once you have answered all the option prompts, dTUNE will
begin reading your source file. dTUNE will print a dot (.) to the
screen for each FIVE lines of code it reads. dTUNE will notify
you of its activities as it creates the desired files. If you
selected the cross-reference option, dTUNE will update you during
the cross-reference at 100 line intervals.

==== GENERAL NOTES ====

dTUNE was written in Borland International's Turbo Pascal,
Version 3.0 and is compiled for operation in a minimum 44K TPA.
This will allow dTUNE to execute succesfully under most keyboard
redefinition programs.

During execution, dTUNE creates at least one (two if you
decide to alter the case of the .TXT file) working file(s). You
MUST ensure that there is sufficient disk space for all working
files, and all desired output files on the default (selected)
drive! Failure to heed this will result in the crash of the
program.

dTUNE will read crunched (i.e. Run-Time (tm)) command files,
but will not alter them. Likewise, it will not cross-reference
crunched command files.


==== LICENSING TERMS ====

dTUNE is Copyright (C) 1984, 1985 by UCS, inc.
ALL RIGHTS ARE RESERVED.

dTUNE is released for PRIVATE NON-COMMERCIAL use only.
Single-User Commercial Use rights are available for a nominal fee
from the author. Private End-users may register dTUNE for a fee
of $25.00, which will entitle them to notification of updates to
dTUNE and limited support. Owners of commercial use rights will
also receive notification of upgrades and limited support.

dTUNE is protected by United States Copyright Law and
International Treaty. Violators of the UCS, inc. copyright will
be prosecuted.


==== CREDITS ====

dBASEII and dBASEIII are trademarks of Ashton-Tate

dTUNE, like most programs, is a result of evolution. Many
people were involved in the testing and modification of dTUNE to
bring it to its present state. These brave pioneers provided the
Beta-Testing and recommendations for improvement that resulted in
dTUNE Version 3.1.

I specifically wish to mention Terry Carroll of Bedford,
Texas, Dr. Don Saba of San Diego, California, Steve Aidikonis of
Streamwood, Illinios, and Fr. Dick Driscoll of Phoenix, Arizona
and express my gratitude for their patience and knowledge of
dBASEII.

mention Terry Carroll of Bedford,
Texas, Dr. Don Saba of San Diego, California, Steve Aidikonis of


 December 21, 2017  Add comments

Leave a Reply