OPENDIR, NEXDIR, CLOSEDIR issue (GRX)

Chris Sellitto sellich at guaranteedreturns.com
Tue Jul 21 08:08:55 PDT 2009


> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Monday, July 20, 2009 5:38 PM
> To: Chris Sellitto
> Cc: filepro-list at lists.celestial.com
> Subject: Re: OPENDIR, NEXDIR, CLOSEDIR issue (GRX)
> 
> Chris Sellitto wrote:
> [...]
> >> Given that line 206 works, and 205 (when changed to "*.*" just like
206)
> >> doesn't, I would first look at the actual directories
> >> "\\server1\d$\FTPFOLDER\extranet\DMLSSFTP" as compared to
> >> "\\server1\d$\FTPFOLDER\extranet\rob".
> >>
> >> What's different about them that might cause a difference in
filePro?
> >
> > I have to be honest with you Ken, I cannot find anything different,
or out
> of the ordinary
> > between these 2 folders, aside from the fact that they have
different
> amounts of files
> > within them.  Could it be that some of the characters are being
resolved
> because of the
> > backslashes?
> 
> As I recall, there was a problem if the directory contained more than
999
> files matching the wildcard, in that opendir() would return the number
> modulo 1000.  (Though nextdir() would return the entire set of files.)
But,
> unless there were an exact multiple of 1000 *.csv files, and exactly 2
more
> than an a multiple of 1000 *.* files, I find this unlikely as the
cause.
> 
> As for backslashes, that shouldn't be an issue.  However, if you are
> concerned about it, simply change them to forward slashes.
> 
> --
> Kenneth Brody

All,

I figured out what my problem is.  If it was any more obvious it would
have bit me in the arse.
Turns out that the filenames in the folder were all longer than 32
characters.  The NEXTDIR()syntax
clearly states that the filename field is a 32 character field.  So it
seems that it will 
ignore any files that exceed this limit.  Once I renamed these files,
and shortened them they
were picked up.  I will now have to come up with a new naming
convention, which I really don't want to
do, because it is very descriptive as to the contents of the file.  Is
there something I can do to overcome
the 32 character filename convention?

Thank you
Christopher Sellitto


More information about the Filepro-list mailing list