Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!raybed2!rayssd!anomaly!mpd
From: mpd@anomaly.sbs.com (Michael P. Deignan)
Newsgroups: comp.databases
Subject: Re: Clipper 5.01 error message
Keywords: Clipper Arghhhh
Message-ID: <1991May17.013633.8848@anomaly.sbs.com>
Date: 17 May 91 01:36:33 GMT
References: <1991May7.235644.28744@gmuvax2.gmu.edu> <1991May8.205744.20911@pegasus.com> <1991May10.112405.7053@anomaly.sbs.com> <1991May15.203838.22946@pegasus.com>
Organization: Small Business Systems, Inc., Esmond, RI  02917
Lines: 51

tleylan@pegasus.com (Tom Leylan) writes:

>Seriously if you use nothing else but logic, how do you explain the 1000s of
>other Clipper developers who are using 5.01 successfully ?  You can't think
>that I'm doing it wrong since I don't crash.

Easy. Nantucket wants to insure a "bug free" release, and the best way to
insure that is to implement the policy of stating every tech support call
is a "problem with your program".

If I have a problem in my code, then why can:

	1. I take a binary, run it with set keystrokes, and have it:

	   a. "hang" entirely forcing a hard-reset
	   b. return some totally bogus "Unrecoverable error 415:
		Unable to open overlay file '[happy-face]'

	2. Then re-compile the modules with the '/b' switch, making no
	   code changes whatsoever, and have the new binary wrun fine
	   with the same exact keystrokes.

Or:

	1. Run a binary requiring 319k to start (according to .RTlink)
	   run okay with 420k,

	2. The same binary in 390k yields an "eval stack fault", scaring
	   the shit out of the user. No simple "insuffienct memory" error,
	   no, lets get fancy here.


Of course, based upon the statements by other Clipper 5.01 users on this
newsgroup, I'm not the only person having this problem. And I daresay that
others out there are having problems too.

Many users still haven't gotten their upgrades. The 5.01 that I am using
was received two weeks ago, and a client with a copy still hasn't received
their upgrade. So, exactly how many people ARE running 5.01?

I tend to believe that the problem is in the link editor, not in the 
Clipper-produced code itself. However, there ARE still problems, and
Nantucket better address them soon, or they will end up looking like
the Ashton Tate of 1991.

MD
-- 
--  Michael P. Deignan                      / Since I *OWN* SBS.COM,
--  Domain: mpd@anomaly.sbs.com            /  These Opinions Generally
--    UUCP: ...!uunet!rayssd!anomaly!mpd  /   Represent The Opinions Of
-- Telebit: +1 401 455 0347              /    My Company...