Microsoft KB Archive/171474
Article ID: 171474
Article Last Modified on 11/18/2003
- Microsoft Visual Basic 5.0 Learning Edition
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
This article was previously published under Q171474
Saving a project to one network share and creating the exe on a different network share causes Visual Basic to generate an invalid path to the EXE file.
This problem is caused when Visual Basic attempts to store the path to the EXE relative to the Project files.
Keep EXE and Project on same share or upgrade to Visual Studio 97 Service Pack 2.
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2.
For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why
For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2
Steps to Reproduce Behavior
This requires two machines;
Create two shares on a system, for example:
- From a second machine, create a new standard EXE project.
- Save the project file and Form1 to \\MyComputer\Share1.
- Build an EXE and save it to \\MyComputer\Share2.
- Close the project.
- Re-open the project.
- Choose Build Exe from the file menu.
In the Build EXE dialog window, note that the path to the EXE is incorrect; the path appears as:
\\<Path to Project>\..\<Path to Exe>.Exe
Without changing anything, click OK. You will receive an error:
"\\<Path to Project>\..\<Path to Exe>.Exe The filename is not valid"
Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171474