Did you have a chance to locate more details on issues with DIRECTORY().

Thanks...Randy

>>>>DECLARE aFiles[1,5]
>>>> IF ADIR(aFiles,lcRoot+lcFolder,'D')=1
>>>> * There's a file or folder
>>>> IF 'D' $ aFiles[1,5]
>>>> * it's a folder
>>>> ELSE
>>>> * there's a file with the name
>>>> ENDIF
>>>> ELSE
>>>> * There's no file or folder that matches
>>>> ENDIF
>>>>
>>>>
>>>>Thanks Ed, that works Great!
>>>
>>>And it's more reliable than DIRECTORY() in VFP5 as well. George Tasker has a class that handles some shortcomings of ADIR() in the files section as well; if you have problems with directories related to multiple '.' characters in file/directory names, his class works.
>>
>>Can someone send me this class (and/or list of shortcomings) in DIRECTORY().
>
>I've gotten inconsistant results in network environments with UNCs and DIRECTORY(), especially with Novell networks. I'll email you details on a couple of specific examples from my office tomorrow; since the ADIR() code works across all the environment, I've simply adjusted to use that approach.
>
>George's code can be downloaded from the files section here under the topic Win32 API as Windows File Names
>>
>>
>>Thanks...Randy