Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!usc!hacgate!ashtate!dbase!awd
From: awd@dbase.UUCP (Alastair Dallas)
Newsgroups: comp.databases
Subject: Re: dBASE IV -- Trials and Tribulations
Summary: Another explanation
Keywords: bugs
Message-ID: <168@dbase.UUCP>
Date: 18 Jul 89 22:52:22 GMT
References: <2071@hub.UUCP> <167@dbase.UUCP>
Organization: Ashton Tate Devlopment Center Glendale, Calif.
Lines: 24

In article <167@dbase.UUCP>, awd@dbase.UUCP (Alastair Dallas) writes:
> In article <2071@hub.UUCP>, erbo@lime.ucsb.edu (Eric J. Bowersox) writes:
> > 
> > BUG #1:	The Case of the Missing Procedure  (or: Son of Line Eater? :-) )
> > 
> > If you have a .PRG file with more than about 8 procedures in it, and you
> > try to call the last procedure in that file, dBASE won't find it, and will
> > hand you a "File does not exist" error.
> 
> ...Is it possible your code is unusual enough that the
> nesting on RETURN statements looks okay to you but looks different to dBASE?
> (That's fairly unlikely, though...

The software designer here who is actually responsible for procedures had
a better explanation.  He points out that dBASE III PLUS (and IV to be 
compatible) will allow duplicate procedure names and that only the first
procedure encountered will then be "found."  Procedure names are case-
insensitive and silently truncate (I think) at some limit (approx. 10),
thus MyProcedureName and MYPROCEDURENAME2 are identical; the compiler
generates no warning about this (maybe it should).

Hope it helps.

/alastair/