The documentation doesn't specifically state that the filename MUST be legal and that the file must exist. The documentation regarding the nMSdOSPath parameter infers that a non-existant filename will be handled ...as if the file had been found in the current default directory even when the second parameter is not used.

The behavior of FULLPATH in VFP6, SP5 is to return the CWD and filename in the same manner as when the nMSDOSPath parameter is used. The VFP6, SP5 version works as expected. It appears that the VFP7 implementation has a problem expanding the length of the return string when the cFileName1 parameter contains quotes and a multiple word filename.

>Yes, FULLPATH() returns strange result in VFP 7 in this case. Still, I don't understand why are you checking for file named "Test File.txt" (with quotes) when the actual file name doesn't have quotes in it?

It's a trade secret ;)

- Keith Payne

>
>>This little guy popped up in my APP launcher when I recompiled with VFP7:
>>
>>

>>local lcFileName
>>
>>if !directory("Fullpath Bugtest")
>>	mkdir "Fullpath Bugtest"
>>endif
>>
>>set default to "Fullpath Bugtest"
>>if !file("Test File.txt")
>>	strtofile("This is a test","Test File.txt")
>>endif
>>
>>lcFileName = chr(34)+"Test File.txt"+chr(34)
>>clear
>>
>>? "Original Filespec: "+lcFileName
>>? "Filespec with FULLPATH: "+fullpath(lcFileName)
>>
>>set default to ".."

>>
>>Run this in VFP7 and VFP6, SP5 and the results are different.
>>
>>VFP6, SP5 Version 06.00.8961.00
>>VFP7 Version 07.00.0000.9262