BUG: Long Project Name is Converted to a Short Project Name

Last reviewed: March 3, 1998
Article ID: Q179857
The information in this article applies to:
  • Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 5.0

SYMPTOMS

A Visual Basic standard executable project is assigned a long filename. When you open this project file from the Windows Explorer instead of from the Visual Basic IDE, the project filename is shortened to an 8.3 format. When you execute the Save As menu command, the short filename is used as the default. Additionally, if you access the Path property of the App object, the path is returned in the 8.3 format.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Start a new Standard EXE project in Visual Basic. Form1 is created by default.

  2. Change the Name property of the project to a long filename, such as LongProjectName.

  3. Save the project and exit Visual Basic.

  4. From the Windows NT Workstation Explorer, double-click the project file you just saved to open the project in Visual Basic.

    BUG: The filename appears in the Project Explorer as a short filename. For example, if you saved your project as LongProjectName, the project name appears as LongP~1 in the Project Explorer. If you execute the Save As menu command, the default file name is also LongP~1.


Additional query words: lfn long file name long filename short file name
short filename App.Path
Keywords : vb5all VBKBDesignTime VBKBEnv VBKBVB
Version : WINDOWS:5.0
Platform : WINDOWS
Issue type : kbbug


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: March 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.