When you remotely run an executable (.exe) file built in Visual FoxPro, using a universal naming convention (UNC) name tha contains spaces, you may receive the following error message:
File <filename> does not exist.
The number of characters in the UNC name does not seem to matter; the spaces in the name cause the error.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in the latest service pack for Visual Studio 6.0.
For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
INFO: Visual Studio 6.0 Service Packs, What, Where, Why 194295
HOWTO: Tell That a Visual Studio Service Pack Is Installed
To download the latest Visual Studio service pack, visit the following Microsoft Web site: