Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : TN9011.ZIP
Filename : ETC.TXT

 
Output of file : ETC.TXT contained in archive : TN9011.ZIP
Etc.

Control Center Booster

A new utility is on the horizon, highly functional and surprisingly
affordable coming to you from Ashton-Tate Developer Services.

Control Center Booster was shown at the 1990 Technical Conference and
was a big hit. At a purchase price of a mere $19.95, the product is
already generating a great amount of interest.

Control Center Booster is an enhancement utility comprised of a main
dBASE IV program, template files and .bin files that join together to
give you several new features in the Control Center and Design
surfaces. The program incorporates several UDFs to give more freedom
of design to the user.

With the use of MAKELOOK(), an entirely new menu of data validation
choices becomes available when constructing screen forms. In this new
menu, one can assign lookup files, index tags and fields. You can
display picklists, add shadowing and assign window dimensions.

dBASE IV provides its own context-sensitive help that is available
just by pressing the F1 key. When you create your own data entry
screens, there is no help available since dBASE IV can't possibly know
your intent. With Control Center Booster, you can easily create your
own custom context-sensitive help for each field in a database that
can be used from within your data entry form. After which, the F1 key
responds to your own help screens which can be as simple or complex as
you want them to be.

In QBE, Control Center Booster allows for cross tabulation. By using
CROSSTAB(), a popup window allows you to plug in information on title,
x-axis and y-axis fields, summary fields and type of operation to
perform.

Designing a database by form allows you to consolidate the process of
creating a structure and then creating a custom screen form. Using a
new template file for screen design, Control Center Booster allows you
to create a .dbf file structure while you design a screen form, making
the process of data base creation much more efficient.

Have you ever been in the midst of designing a screen when you needed
to test out a calculated field or a UDF? The discouraging factor was
that you would first have to take the time to save and compile your
screen form. Control Center Booster once again, provides a
time-saving measure with the inclusion of the UDFs ED() and DOT() to
give you access to the program editor or dot prompt while within a
design work surface.

Since new template files become available from time to time (Control
Center Booster provides an additional two .gen files itself), the
TEMPLATE() function allows you to switch .GEN files from within dBASE
IV work surfaces so that you can freely switch back and forth to
specialized custom template files.

Control Center Booster is available through Customer Service.
Technical Support for this software is provided exclusively through
the Ashton-Tate BBS /TEMPLATE SIG by its authors Bill Ramos and Kirk
Nason.

Between Versions

Inevitably, when an update is received, many users find themselves in
a Catch-22 of wanting to install the new software but lacking the time
to make the change-over. Consequently, many decide to install the new
version along side their existing previous version until they can make
a full transition. This can lead to trouble unless you're careful.

The problems stem from the DOS path which leads to both directories in
which the different versions exist. The result can be one version
inadvertently using overlay files from the other version. The
problems arise in various forms but ultimately results in chronic
strange behavior in the operation of dBASE IV.

The solution to this problem is in the form of a batch file that can
manage the path process of multiple versions.

SET OLDPATH = %PATH%
SET PATH=E:\DB411;%OLDPATH%
C:
CD \DATADIR
DBASE/T
CD\
SET PATH=%OLDPATH%
SET OLDPATH=

Here's what occurs in the batch file, step by step:

1. We make a copy of the current PATH environmental variable by
assigning that string to the OLDPATH variable.

2. Then, the path to the directory of the version we wish to run
is added to the OLDPATH variable, placed in front so the files in that
directory will be considered first. (Since DOS searches the path from
left to right, performance is improved overall if the desired
directory is first in the list).

3. We navigate to the directory containing the data to be used.

4. Invoke dBASE IV.

5. Move back to the root directoryÄor wherever you choose.

6. Assign the original path from OLDPATH back to the PATH
variable.

7. Free up space in the environment by "deleting" the OLDPATH
variable (assigning it to a null value).

Questions on this procedure can be directed to Steve on the
Ashton-Tate BBS. See the back page masthead for protocol and phone
numbers.

Technical Tips on Installing dBASE IV version 1.1

Your Serial Number

During the dBASE IV installation process, you will be requested to
enter your dBASE IV serial number. To ensure easy accessibility to
your serial number, it is important before beginning the dBASE IV
installation program that you write down the serial number found on
System Disk 1 on 5.25" disks, or on the Installation Disk on 3.5"
disks.

For customers who are updating from dBASE IV version 1.0, your dBASE
IV serial number will be shown as ON FILE on your dBASE IV version 1.1
System Disk 1 or Installation disk. This indicates that your previous
version 1.0 serial number is on file with Ashton-Tate and now applies
to your new version 1.1. You should type in your version 1.0 serial
number exactly as written on your version 1.0 System Disk 1 or
Installation Disk. You will also find your dBASE IV version 1.0
serial number on the bottom of your dBASE IV version 1.0 product
slip-case.

Using Quick Install

The Quick install procedure automatically installs the single-user
dBASE IV system files as well as the SQL, sample, and tutorial files.
It is important to ensure that before using the Quick install
procedure you have at least 6 MB of free disk space available. You
may use the Full install procedure to selectively install SQL sample,
and tutorial files.

dBASE IV Temporary File Storage

dBASE IV must be able to open a 300K temporary file on the default
disk when it starts up. If dBASE IV cannot open this file
successfully, you will receive the message Unable to write on temp
file . You can use the TMP or DBTMP
environment variables to control the location of the temporary file,
to assure that it is written to a readable and writable drive and
directory with sufficient space.

Installing dBASE IV to the Root Directory

You should not try to install single-user dBASE IV to the root
directory. dBASE IV should be installed in a sub-directory, for
example, \DBASE.

If you do attempt to install dBASE IV to the root directory you will
find that the dBASE.OV4, .OV5, .OV6, and .OV7 files will not be copied
correctly in order to form dBASE.OVL. To properly build the overlay
file if this occurs you may use the DOS copy command in the following
way:

COPY DBASE.OV4/B+DBASE.OV5/B+DBASE.OV6/B+DBASE.OV7/B DBASE.OVL

We recommend that you do not install single-user dBASE IV to the root
directory, particularly as DOS only allows a maximum of 512 files in
the root of any drive.

What's My Line?

Screen display problems may be seen during the installation and
running of dBASE IV on certain AT&T and Olivetti computers. The
problems occur most often when these machines have CGA cards and
specific BIOS versions.

During the installation of dBASE IV, the default video mode is
erroneously set to 43 lines. However, since only 25 lines can be
displayed on this machine, the bottom 18 lines are not visible. This
means that during installation of dBASE IV, any messages that appear
on the bottom of the screen (such as Press any key to continue) are
not visible to the user.

Similarly, within dBASE IV, at the dot prompt or in ASSIST, only 25
lines are visible on the screen and the bottom 18 lines are not
visible.

The machines against which the problem has been reported are: AT & T
6300 with BIOS versions of 1.17 and 1.43, Olivetti M-21 and M-24
computers, and the Xerox 6060 with BIOS version 1.36. The computer's
BIOS version will display on the screen in the upper left during power
up. This problem is related to a change in the method that dBASE IV
uses to check the current video mode and an inherently incorrect
setting of a byte in memory that describes the current video mode as
set by the ROM BIOS of these particular machines.

To resolve this problem, a small program has been developed to switch
this byte to a value that correctly indicates the current video mode
(CGA) on these computers. This program, FixVid.com is available for
downloading from the Ashton-Tate Bulletin Board. The program can be
run daily from the Autoexec.bat file, or from a batch file just prior
to entering dBASE IV.

It is also quite simple to create the .com file using the following
dBASE commands run at the dot prompt will create FixVid.com:

_pdriver="ASCII"
SET PRINTER TO FILE fixvid.COM
??? "{49}{192}{142}{216}{198}{6}{132}{4}{0}{195}"
SET PRINTER TO

If you desire to use this method to create FixVid.com, after a
successful installation from the dot prompt within dBASE IV, first
issue the command RUN CLS. This will cause the video mode to be reset
during the current dBASE IV session. After FixVid.com has been
created, quit dBASE IV and run FixVid from DOS. Running FixVid from
the Autoexec.bat file will cause it to be invoked each time the
computer is booted. This will allow dBASE IV to display properly
every time it is run.



  3 Responses to “Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : TN9011.ZIP
Filename : ETC.TXT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/