Borland dBASE IV  Version 2.0 and dBASE Compiler for DOS

Software Review by Frank Murphy

The dBASE IV program has been around since 1988. The original
version became instantly famous for its lackluster performance.
Three updates later and with a new owner, dBASE IV is finally able
to compete favorably with any database program in the market place.

Old-time dBASE users who are comfortable with the Control Center
will be happy to learn that the user interface hasn't changed.
Present are the same familiar 6 panels that give us access to the
types of files and tables used by dBASE (data, queries, forms,
reports, labels and applications).

Apart from a few minor changes on the pull down menus, it's hard to
tell the difference between version 2.0 and version 1.5. That is
until you start working with large databases. Compared with
previous versions this product really "moves out." (Borland claims
a10 fold increase in speed over version 1.5.)

The significant changes are all "under the hood." Here are a few
examples of the improvements: Optimized queries, high performance
filters, improved mouse support, and better memory management (if
available, extended memory is used for the swap file).

The form designer has been enhanced. One can now use the mouse to
drag and drop selected fields or text on the screen. It's not as
slick as the FoxPro screen designer, though.

Programmers will be pleased the new commands added to the language.
There are new commands for pop-up menus, menu pads and for
controlling mouse events.

Bottom line. If you like the "feel" of dBASE IV 1.5 but wished it
had a little more "oomph," then version 2.0 is for you. List price
is $795. Upgrade price is $99.95.

The long awaited compiler for dBASE has finally arrived. Users who
purchased the Developer's Edition from Ashton-Tate were promised a
compiler "real soon now." That was five years ago. Borland has made
good on the promise.

The Borland dBASE compiler translates source modules into
pseudo-code object files. Developers can choose to build standalone
or compact .EXE files.

The standalone is a fully functional .EXE that doesn't require any
additional dBASE system files. The .EXE incorporates the library
and resource files. The compact executable does not include the
runtime library and resource files. Users can run compact
executables only if they have the appropriate runtime files.

Which form should you use? Standalone .EXE files are HUGE. If a
developer needs to distribute only one EXE, the standalone form
would be appropriate. However if more than one EXE needs to be
distributed, it would better to create them in compact form and
include a copy of the runtime libraries in the final package.

I did a comparison of file sizes using the infamous "Hello World"
program. (The only function of the program is to display Hello
World on the screen.)

Compiling the program as a standalone resulted in a 1.8MB
executable! The compact form came out at 154KB.

For comparison purposes I compiled the same program with Clipper
version 5.2. The result was a 158KB standalone .EXE. Although the
size was slightly greater than the dBASE compact, the Clipper
program loaded faster because it didn't have to contend with
runtime libraries. Of course Clipper does not claim to be 100%
compatible with the dBASE language.

The bottom line: if you're a dBASE IV developer and wish to
distribute executables to users who do not own a copy of dBASE, the
new Borland dBASE compiler may be what you need.

The list price for the compiler is $495. It's free to registered
users of the dBASE IV Developer's Edition. Call Borland
International at 800-331-0877, extension 1027 for details.