Chdir problem

GCC Consulting gcc at optonline.net
Wed Sep 1 18:12:02 PDT 2004


 

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com 
> [mailto:filepro-list-bounces at lists.celestial.com] On Behalf 
> Of Kenneth Brody
> Sent: Wednesday, September 01, 2004 8:11 PM
> To: rkreiss at gccconsulting.net
> Cc: 'filePro Mailing List'
> Subject: Re: Chdir problem
> 
> GCC Consulting wrote:
> [...]
> > Using those names, check for the file 997.rpt and see if it had the 
> > current date.
> > 
> > So, this is how directory structure for one customer would look
> > 
> >         c:/edata/Geis-A/macy/ANSI/997/all/997.rpt  
> (remember windows 
> > and fp will translate the / to a \)
> >                       ^^^^
> >                      this name changes
> 
> Actually, no translation is done or needed, as Windows works 
> just fine with forward slashes.
> 
> I'm not sure which part of the name changes, since your 
> arrows point to the path separator.  I'll assume for now that 
> "macy" is the part that changes.
> Adjust this as needed.
> 
> Use opendir/@dirlist/closedir to read everything in the 
> "c:/edata/Geis-A"
> directory.  You can then build the fill path and use EXISTS() 
> to see if the file 
> "c:/edata/Geis-A/"{name{"/ANSI/997/all/997.rpt" exists.  If 
> it does, you can then use @FSTAT[] to check the modification date.
> 
Ken,

Your assumption is correct, the arrows were supposed to point to macy.

997.rpt should exist in each directory.  It will be the modification date that
will be important.

Again, thank you for your advise on how to best handle this problem.

Richard Kreiss
GCC Consulting




More information about the Filepro-list mailing list