>There are still problems, depending on your code. I'm currently fighting a bug with long file names. IMO, the best solution would be for VFP to internally call GetShortPathName() for anything using a filename. In the meantime, I've having to put this call into LOTS of code.
>
>>>Hi, Is there a work around to allow working with file names that include one or more spaces? Not sure if VFP 7 does this. Im using Version 6. Thanks
>>
>>FoxPro, up to VFP 6, had problems with UNC, when the computer name, any folder on the path, or the filename had spaces.
>>
>>The problems ("EXE can't be found") didn't appear on local or mapped drives, and were fixed in SP4.
>>
>>I am not sure if your problem is related with this.
>>
>>Hilmar.
Are your problems related to spaces / special characters only?
I use LFN for table names, and others, but only use characters, underscores and digits, for safety. I had no problem thus far.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)