Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!ames!elroy!hacgate!ashtate!dbase!awd
From: awd@dbase.UUCP (Alastair Dallas)
Newsgroups: comp.databases
Subject: Re: dBase question
Summary: New SCAN command
Message-ID: <50@dbase.UUCP>
Date: 12 Apr 89 16:28:53 GMT
References: <6666@bsu-cs.bsu.edu> <1325@naucse.UUCP> <22879@agate.BERKELEY.EDU>
Organization: Ashton Tate Devlopment Center Glendale, Calif.
Lines: 30

In article <22879@agate.BERKELEY.EDU>, steve@violet.berkeley.edu (Steve Goldfield) writes:
> In article <1325@naucse.UUCP> wew@naucse.UUCP (Bill Wilson) writes:
> #>>
> #>The continue command should only be used with LOCATE.  When using
> #>seek and find, you simply skip to the next record and check to see 
> #>if the key expression is the same with an if statement.
> 
> Actually, it's probably more efficient to put the SKIP inside
> a DO WHILE CONDITION, rather than to embed an IF statement.
> 

In dBASE IV, you can use the SCAN command.  Instead of what Steve suggests:

SEEK <key>
DO WHILE <key> = value
	<processing>
	SKIP
ENDDO

you can say:

SCAN FOR <key> = value
	<processing>
ENDSCAN

which is a little more elegant.

/alastair/