Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!csd4.csd.uwm.edu!chad
From: chad@csd4.csd.uwm.edu (D. Chadwick Gibbons)
Newsgroups: comp.lang.pascal
Subject: Re: Findfirst
Message-ID: <4955@uwm.edu>
Date: 11 Jul 90 00:25:02 GMT
References: <23854@adm.BRL.MIL>
Sender: news@uwm.edu
Reply-To: chad@csd4.csd.uwm.edu (D. Chadwick Gibbons)
Organization: University of Wisconsin-Milwaukee
Lines: 20

In article <23854@adm.BRL.MIL> elric%FSU@pucc.princeton.edu  writes:
|In regards to the guy who was having the "no more files" error, maybe it is
|obvious - maybe there are no more files.  Also, in the findfirst and findnext
|commands did you search for 'anyfile'?  This could give you problems since it
|also gives you subdirectory names as I discovered the hard way.  You need to
|have it search for 'archive' type files.  Those are the actual files, not
|the subdirectory names.  Hope that helps.

unfortunately, you don't want to do that.  specifing archive files may
seem the right thing to do, but thing of when you backup using any decent
backup system: the archive bits are unset until that file is modified
again.  thus, you can be searching for an file that _is_ there but isn't
archived.

in reference to the other individual: check that you are not corrupting
your search record.  that's a common problem and sounds like the problem
in your case.  be sure your recursive routines allow modification of the
search record or that the search record is a global variable.
--
D. Chadwick Gibbons, chad@csd4.csd.uwm.edu, ...!{rutgers,uunet}!uwm!uwmcsd4!chad