Xref: utzoo comp.databases:2770 comp.sys.ibm.pc:30176
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!xanth!aiko
From: aiko@cs.odu.edu (John K Hayes)
Newsgroups: comp.databases,comp.sys.ibm.pc
Subject: Re: Possible Clipper Bug?
Keywords: Clipper, Bugs
Message-ID: <9235@xanth.cs.odu.edu>
Date: 14 Jun 89 23:21:16 GMT
References: <506@dcscg1.UUCP>
Reply-To: aiko@cs.odu.edu (John K Hayes)
Followup-To: comp.databases
Distribution: usa
Organization: Old Dominion University; Norfolk, Virginia USA
Lines: 37

In article <506@dcscg1.UUCP> drezac@dcscg1.UUCP (Duane L. Rezac) writes:
>
>Hello: 
>
>I recently ran into a problem with clipper, and it appears to be a Bug. Has 
>anyone else ran into this problem (or is it a "feature")
>
>I created an index on a database. after initializing a few variables, I entered
>a processing loop that was coded as :   "do while .not. eof() " In DBASEIII, 
>the program ran fine. In clipper, it bypassed the loop. Upon examination with
>debug, I discovered that after Clipper finished indexing the file, it left 
>the database at eof, with eof()=.T. (of course, this caused the do while .not.  eof() to fail ;-( ) a "goto top" inserted after the index command corrected the
>problem. 
>
>Has anyone else ran into this type of problem? It appears that after Clipper 
>indexes a file, it leaves it at eof. 
>
>Duane L. Rezac




From my experience with clipper (I've been using it everyday for over a year no)
it leaves the record pointer at the top of file after indexing.  Of course, I
have only used two versions: Summer '87 and Autumn '86.  Both of these have
working the same way dBASE does with respect to indexing and the pointer.

-- 
    ---{john hayes}  Old Dominion University; Norfolk, Virginia USA
                     internet: aiko@cs.odu.edu
                     Home: (804) 622-8348     Work: (804) 460-2241 ext 134  

                      <++++++++++++++++++++++++++++++++++>
Are you a Have or a Have_Not?  Because if you're a Have_Not, you've probably
had it; whereas, if you're a Have, you've probably got it and are going to 
give it away at some point in the future!       --- The Clash
                      <++++++++++++++++++++++++++++++++++>