Xref: utzoo comp.databases:2731 comp.sys.ibm.pc:29955
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!dsacg1!dcscg1!drezac
From: drezac@dcscg1.UUCP (Duane L. Rezac)
Newsgroups: comp.databases,comp.sys.ibm.pc
Subject: Possible Clipper Bug?
Keywords: Clipper, Bugs
Message-ID: <506@dcscg1.UUCP>
Date: 9 Jun 89 12:21:25 GMT
Distribution: usa
Organization: Defense Construction Supply Center, Columbus
Lines: 17


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