>>Try this series of VFP commands:
>>
>>

>>x = fullpath('')
>>? fullpath('','')
>>? fullpath('','')
>>

>>
>>Note that the first result from fullpath('','') is blank (wrong!), but the second result correctly displays the current directory. All subsequent results are consistently correct, but for some reason, having immediately preceded the first invocation by the initial assignment statement that refers to fullpath('') screws up the immediately following result from fullpath called with 2 arguments. The same problem occurs for any path specified in the second argument.
>>
>>I've tested this under both VFP6SP5 and VFP7SP1, XP Pro SP1. Please confirm, do others see this nasty bug, and does it still exist in VFP8SP1?
>>
>>Mike
>
>Why is this a bug? I would expect FULLPATH('') should be blank, since no file name was passed.
>Using that expectation, it is now a bug in VFP8SP1 :)

Whatever your expectation, Trey, you shouldn't be too happy about the fact that the same command yields two different results. Your tag line says it all.

Mike