PRB: Long File Names are Converted to Short by Association

Last reviewed: October 13, 1997
Article ID: Q150706
The information in this article applies to:
  • Microsoft Visual Basic Control Creation, Learning, Professional, and Enterprise Editions for Windows, version 5.0
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0
  • Microsoft Windows 95

SYMPTOMS

Opening a Visual Basic project with a long file name, using any method other than starting Visual Basic and then opening the project, results in Visual Basic opening the project using the short file name, causing the short file name to appear on the title bar of the project.

STATUS

This behavior is by design.

RESOLUTION

Perform the following steps to resolve the problem:

  1. Start Windows Explorer. From the View menu, select Options.

  2. Click the File Types tab. Double-click Visual Basic Project in the Registered file types list box. The Edit File Type window appears.

  3. Double-click Open in the Action list box. The Editing action for type: Visual Basic Project dialog box appears.

  4. In the Application used to perform action: text box, put quotation marks (" ") around the Command line for Visual Basic. The text should look like the following:

          "C:\ProgramFiles\Microsoft Visual Basic\vb32.exe" "%1"
    

  5. Click OK, and close all windows and dialog boxes.

Now when you open a Visual Basic project with a long file name, the long file name appears on the title bar of the project.


Additional query words: win95
Keywords : PrgCtrlsStd VB4ALL VB4WIN vb5all
Version : WINDOWS:4.0,5.0;WINNT:4.0
Platform : NT WINDOWS
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 13, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.