Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!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: <1991May19.022917.7632@anomaly.sbs.com> Date: 19 May 91 02:29:17 GMT References: <1991May13.223912.1975@gmuvax2.gmu.edu> <1991May15.110418.5031@anomaly.sbs.com> <1991May17.215929.18795@pegasus.com> Organization: Small Business Systems, Inc., Esmond, RI 02917 Lines: 72 tleylan@pegasus.com (Tom Leylan) writes: >That application that you sold me is blowing up with random "variable not >found" errors... >Notice how easy it is to lie ? Is this an indictment that I, and others in this newsgroup, are lying about the problems we've encountered with 5.01a? >Why don't I get the same errors ? Why >don't thousands of others get the same errors ? Quite possibly because your code doesn't involve the level of sophistication that ours does? Perhaps we're writing something other than "hello world" programs with Clipper? >There could be many reasons for you getting these errors (including the >possibility of bugs in 5.01) but there are plenty of others. You could be >using an older copy of Blinker or Warplink that doesn't support 5.01. Since you're such a good friend with the author of Blinker, you should know this is an impossibility since Blinker yields invalid "COMDEF" errors when used with 5.01a. In case your friend forgot to mention it, you can call Blinkinc tech support and get a recording indicating such. >You >could be linking in routines from Funcky or 3PX or any of two dozen other >function libraries (Netlib perhaps ?) that hasn't been updated to 5.01 yet. Sorry, 100% Clipper code. No external libraries... >You could be referencing your own C or assembler routine and could be messing >with registers, you could have old S'87 code in a library along the path that >is getting linked in. ...or C/Assembler code... >So the question remains why is it that so few people I know are having problems >and the majority that do find that they in fact misunderstood the way that >STATIC variables or codeblocks operate and report success as soon as they >make the adjustment ? I don't consider the message "Unrecoverable Error 415: Unable to open overlay file ''" to be a simple "misunderstanding" of how code blocks function. >At what point will you accept the likelihood >that you are mistaken ? I won't, since the problem is intermittent, and gets resolved by re-linking the application. So, when I can re-link an application and get rid of the problem WITHOUT MAKING A SINGLE CODE CHANGE, *that* tells me there is something wrong with the development software. >I'll tell you when Nantucket will... the moment that >you isolate the problem into a reasonable amount of code and submit it to >them as a bug. Or, when hundreds of other people begin to experience the same problem. When the database community decides to send Nantucket the route of Ashton Tate. 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...