Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!ames!ucsd!nosc!humu!pegasus!tleylan
From: tleylan@pegasus.com (Tom Leylan)
Newsgroups: comp.databases
Subject: Re: Help: Clipper linker information needed soon
Message-ID: <1991Apr1.005555.29136@pegasus.com>
Date: 1 Apr 91 00:55:55 GMT
References: <1991Mar27.051659.12850@colorado.edu> <25097@hydra.gatech.EDU>
Organization: Pegasus,  Honolulu
Lines: 53

In article <25097@hydra.gatech.EDU> jgb@prism.gatech.EDU (James G. Baker) writes:
>In article <1991Mar27.051659.12850@colorado.edu> haverlan@tramp.colorado.edu (HAVERLAND MARC BRADLEY) writes:
>>I need a replacement linker for Clipper Summer '87.  Clipper 5.0 is giving
>>me "internal errors," (and I'm not using any 5.0 specific things, so that's
>>not a problem).
>
 ... stuff deleted ...

>One note I thought I would mention:  One Tech support person said the 5.0 
>.dbf files are not *exactly* the same as S'87.  This can cause indexing
>problems (it did for me).  Actually create the .dbf from scratch using
>DBU 5.0 (don't copy from, etc).
>
This appears to have changed subjects so I'll try address them both.

Linkers:

 Blinker is available from Blink, Inc., P.O. Box 7154, Richmond, VA  23221
                           (804) 355-4444

 Warplink is available from hyperkinetix, inc., 615 No. Poplar Avenue
                            Orange, CA  92667
                            (714) 935-0823

hyperkinetix address and phone are new starting April 1st.

(if you call either, tell them Tom Leylan sent you)

I don't know who publishes ALINK these days but I know the people who
produced it originally... in fact I'll be seeing him in South Africa next
week.

Now re: internal errors in 5.0.  There are bugs in 5.0 that are causing
errors to occur which should not be occurring.  The tech support people
don't know because there is no reason to explain how the VMM system operates
and the consequences of null pointers.  There isn't anything anyone can do
to stop an internal error since they aren't supposed to be happening.

The fix disk is due any time now and virtually all bugs have been fixed, I
have tested it extensively and can't get it to crash.  Straight S'87 code,
mixed with 5.0 and 5.0 alone.  C code mixed in, assembler mixed in, twist
it, shake it, slam it against the wall it isn't breaking any longer.

As far as I know (and I know a considerable amount) there have been no mods
to the .DBF structure and if anybody has a name as to at Nantucket said so
I'll have it followed up.

I'll be speaking at the June Developer's Conference in Palm Desert on
converting from S'87 to 5.0.  If anyone is considering attending, look me
up.

tom leylan
(ex-Senior Systems Analyst / Nantucket Corp.)