Microsoft KB Archive/281698

= FIX: Error When You Run an Executable File Remotely Using UNC Name with Spaces =

Article ID: 281698

Article Last Modified on 8/7/2007

-

APPLIES TO


 * Microsoft Visual FoxPro 6.0 Professional Edition

-



This article was previously published under Q281698



SYMPTOMS
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 does not exist.

The number of characters in the UNC name does not seem to matter; the spaces in the name cause the error.



STATUS
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:

194022 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:

http://msdn2.microsoft.com/en-us/vstudio/Aa718353.aspx



Steps to Reproduce Behavior
 Build a Visual FoxPro executable file. On another computer, place the file in a folder called &quot;Folder With Spaces&quot; (without quotation marks).NOTE: You can also add the folder to your local computer; just make sure that you use the UNC name of the local computer to run the executable file.

 Click Start, click Run, and then type the following (including the quotes):

&quot;\\\Folder With Spaces\&quot;

The error message mentioned in the &quot;Symptoms&quot; section appears.

 In Windows Explorer, remove the spaces from the &quot;Folder With Spaces&quot; name, and then repeat Step 3 using the new path. The executable file runs without error.

Keywords: kbappsetup kbbug kbfix kbvs600sp5fix KB281698

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.