>>I have a program that locates and moves linked Word documents that users drop all over the network. Unfortunately, FILE() returns .F. for a file with the name such as "John C. Smith Letter.DOC". Files with periods or some other previously disallowed characters aren't recognized.
>>
>>If anyone has a solution or workaround, I would greatly appreciate it.
>>
>>TIA
>
>Dan,
>
>I just tested in VFP6 SP3 and file() works fine as long as the file name is enclosed in quotes, for example;
>
>Given a file named "testing spaces.txt".
>
>?File("Testing spaces.txt") && .T.
>mfile = "Testing Spaces.txt"
>?File(mfile) && .T.
>?File(Testing spaces.txt) && Error missing )

Jim, I haven't tried under SP3, but under earlier versions of VFP, there were some strange and wonderful errors in file name processing, specific instances that i encountered involved LFNs on NetWare 3.x volumes with the OS2 and/or Mac NameSpace enabled. Multiple periods in a file name, or a mix of periods and spaces in a file extension had wierd results. George Tasker also documented some reproducible errors for FILE() and ADIR() that were addressed by using API calls; he has a file handling class that can be downloaded here on UT that gives exact details.