The LA Fox Developer Newsletter

September 1994

Hot Tips (Con't from page 7)

update the .CDX file as well as the .DBF file. In

my experience, however, these are far outweighed

by the advantage of having Rushmore working for

you full time.

(Jim Slater is Vice President of the Rocky Moun-

tain Fox User Group in Denver, Colorado. He has

been developing database applications in dBase,

Fox, FoxBase, and FoxPro for 11 years. He can

be reached on CompuServe at 76367,1735.]

XPro User Group News (Con't from page 5)

3)

Change any calls to SELECTO in Clipper to

WORKAREA() in dBase. Do not change calls to

SELECT(<exp>) as these are still correct.

PRIVATE opened[100] && cannot define arrays

as PRIVATE!

Regarding the PRIVATE memvar[x] issue, I

haven’t tried this myself yet, but I’m doing some-

thing very similar with LOCAL memvars... Try

PRIVATE memvar

memvar = new Array(100)

USING PARADOX FILES WITH DBASE WINDOWS

Some features provided by using Paradox tables

in dBASE for Windows:

>Auto-increment fields automatically create a

primary key value (one higher than the previously

highest value in that field) for you when you add a

record.

>Referential-integnty enforced by the database

>Pnmary Keys enforced by the database

>Ranges (min and max values for a column)

enforced by the database

>Default values for columns of a new record

enforced by the database

>Required fields (no empty value allowed) en-

forced by the database

>Security access enforced by the database

The .DB file format is really quite different than the

(Con't, page 9)

Three From Landmark

by Barry R. Lee

Landmark Research International Corporation

(LRIC) has introduced three new pieces of software to

help make our jobs as developers and consultants a

little easier: WINProbe v3.O, iniExpert, and Landmark

DataSafe.

WINProbe is advertised as a “troubleshooting and

optimization software for Windows”. I gained a more-

than-passing acquaintance with WINProbe while

investigating GPFs and thier causes. In the last issue

of The Developer, when Part 1 of “Navigating the GP

Fault” was introduced, I stated "I tried the latest ver-

sion of WiNProbe and this program caused a GPF of

its own”. Since then, I downloaded a patch that took

the program from v2.I to v2.IC and seemed to fix the

problem of generating GPFs from within itself.

This latest offering from Landmark fixes all of the

previously known bugs and introduces a completely

new user interface and set of functions. Basic system

requirements are pretty simple.... if you can run Win-

dows, you can run WiNProbe.

This program has been designed to give you all of the

information you ever wanted to know about how your

particular Windows installation is performing in terms

of audio, communication, floppy/hard drive, keyboard,

coprocessor, motherboard, mouse, multimedia,

PCMCIA, printer, RAM, and video diagnostics. It also

does an admirable job in providing information related

to BIOS, CMOS, I/O ports, hardware overviews,

memory management tables, network information,

disk utilization, interrupt vector information, device

driver list and capabilities, system resources, and

environmental variables. (Whew! I’m all out of breath!)

Needless to say, this is a pretty extensive program.

Of particular interest are the “Tune-up” and “Windows”

menus. Through these, it is possible to tune up

Windows, clean up .INI files, tune up group files, and

optimize memory and resources.

To this date, WiNProbe v3.O probably represents the

Cadillac of this class of programs. If you need more

sophistication than other programs, such as Checklt’s

Setup Advisor, I highly recommend this program.

(Con’t, page 9)

Page 8