Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!usenet
From: tmkk@uiuc.edu (K. Khan)
Newsgroups: comp.databases
Subject: Re: Clipper 5.01 error message
Message-ID: <1991May20.220734.22320@ux1.cso.uiuc.edu>
Date: 20 May 91 22:07:34 GMT
Article-I.D.: ux1.1991May20.220734.22320
References: <1991May17.210556.18104@pegasus.com> <1991May7.235644.28744@gmuvax2.gmu.edu> <1991May09.090352.17859@anomaly.sbs.com> <1991May16.135400.4616@ux1.cso.uiuc.edu>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 21


In article <1991May17.210556.18104@pegasus.com> tleylan@pegasus.com (Tom Leylan) writes:
>
>I run into
>incompetence every day from the people at Burger King to the people who run
>the U.S. government, it's frustrating but one learns to deal with it.

Ah, so you're saying that I should just "learn to deal with" Nantucket's
incompetence? ;-)

Perhaps jumping into a bitch fest on Usenet *IS* one way in which I deal
with it (if nothing else, it helps to work off the frustrations). It's
also useful to know that other people are having similar problems with
Clipper 5.01 (i.e. "I'm not the only one.")

To MPD and others suffering from Clipper bugs: It happened again. After
I installed the workaround for the first routine which suffered from the
problem, a similar routine in another part of the program ran into the
exact same problem.

Our copy of FoxPro is on its way... :-(