>>>Hi everybody,
>>>
>>>I'm trying to investigate strange problem. If I run this command in command window: "DO MAPREF", it fails with "Data type mismatch" error. Debug shows "Source is unavailable". If I change it to DO MAPREF.APP, it runs my correct file and I don't see an error. The same if I DO MAPREF.PRG. So, I thought, may be I have Mapref.exe somewhere, so I did ?FULLPATH("MAPREF.EXE") and it returned a path, while FILE("MAPREF.EXE") returned .f. and Windows Explorer also don't show this file. I've checked HELP file on FULLPATH() in VFP6, but this "feature" is not mentioned here.
>>>
>>>What is it: Help omission or bug/feature in FULLPATH() behavior? And why am I seeing this strange problem with error?
>>
>>Yes, it's in the help:
>>"If the file can't be located in the MS-DOS path, a path and the file name are returned as if the file had been found in the current default directory".
>
>From the Help:
>nMSDOSPath
>
>Specifies that the MS-DOS path is searched instead of the Visual FoxPro path. nMSDOSPath can have any numeric value. If the file can't be located in the MS-DOS path, a path and the file name are returned as if the file had been found in the current default directory.
>
>I don't specify the second parameter at all, so I assume, that VFP path is searched and this info is not applied... BTW, the Help is vague here...

Yes, it's still applicable to VFP path too.

BTW, why did you post you reply twice? I'm not going to reply to second one. :)