Chdir problem

[Fairlight]

At Wed, Sep 01, 2004 at 08:32:03AM -0400 or thereabouts, 
suspect Kenneth Brody was observed uttering:
> Fairlight wrote:
> [...]
> > You want to look at OPENDIR, NEXTDIR, CLOSEDIR, and EXISTS with the array
> > @FSTAT[] in v5.x.  The first three are only necessary if you need to
> > actually traverse directories.  If you just need to peek at that file in 8
> > locations, you could just use EXISTS and check @FSTAT[].
> [...]
> 
> FYI -
> 
> The opendir/nextdir/closedir/@dirlist[] combo includes the modification
> date and time, so in this case the exists/@fstat[] combo is redundant.

Unless he wasn't needing to do full traversal.  He said he needed to, but
it seemed like there was one specific file he knew would be there, in a
speciic part of a heirarchy where only one segment of a pathname changed.
I'm thinking that a far easier way to do it would simply be with
exists/@fstat[] based on the contents of a lookup to customer or company (I
forget which, and it's been snipped) names that have a field set that they
should be checked for the presence of that file.

I can't tell if it was a complete example, or a hypothetical explanation.
So I tried answering both ways.  But it didn't seem like traversal was
actually needed given the specific example.

("He" being Richard throughout this post...no offense, I know you're
"sitting right here", Richard.  No disrespect intended.)  :)

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html