>>FILE() searches the VFP search path, while FOPEN() does not
>
>That's the first thing that I thought of when I read the original message. But I tested it and it's not true (and the Help file also confirms this)... FOPEN() *does* use the VFP search path.
>
>So the problem is most likely a sharing violation when attempting to open the file.
>
>Best...
>
>--Brad\
I think this is just one more reason to never use FILE() in cases like this. Always use ADIR() with the exact path (as stated in many posts to UT). It only looks where you tell it to look.