Article ID: 281698 - View products that this article applies to.
This article was previously published under Q281698
This article has been archived. It is offered "as is" and will no longer be updated.
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:
The number of characters in the UNC name does not seem to matter; the spaces in the name cause the error.
File <filename> does not exist.
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:
194022To download the latest Visual Studio service pack, visit the following Microsoft Web site:
(https://support.microsoft.com/kb/194022/EN-US/ )INFO: Visual Studio 6.0 Service Packs, What, Where, Why
(https://support.microsoft.com/kb/194295/EN-US/ )HOWTO: Tell That a Visual Studio Service Pack Is Installed
Steps to Reproduce Behavior
Article ID: 281698 - Last Review: October 21, 2013 - Revision: 1.2