DOCUMENT:Q191005  07-AUG-1998  [vbwin]
TITLE   :BUG: EXE Created Without File Extension on Windows 98
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:
OPER/SYS:WINDOWS
KEYWORDS:

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic Learning, Professional, and Enterprise Editions
   for Windows, version 6.0
   on the following platform: Win98
---------------------------------------------------------------------

SYMPTOMS
========

Creating an EXE in Visual Basic on Windows 98 creates a file without a .EXE
extension. Attempting to run the application by clicking on the filename
within Windows Explorer opens a dialog asking you to "Open With...",
providing a list of installed applications.

CAUSE
=====

The .EXE file created does not have a .EXE extension, therefore Windows
does not know how to open the file. The file extension will not be created
if the following conditions are true:

 - The Windows Explorer setting "Hide File extensions for known file types"
   is set to the default value of True.

 - The Windows Explorer setting for Hidden Files is set to the default
   option of "Do not show hidden system files."

 - The above two settings have never been changed from their default
   values.

RESOLUTION
==========

To work around this problem, change the Windows Explorer setting for "Hide
File extensions for known file types" and change the Hidden Files option to
something other than "Do Not show hidden or system files."

Step-by-Step Example
--------------------

1. Open Windows Explorer. Choose Folder Options from the View menu.

2. Select the View Tab. Deselect the "Hide Files extensions for known file
   types."

3. Change the Hidden Files option to something other than "Do not show
   hidden or system files."

   If you change the above two settings on Windows 98 from their defaults
   and then set them back again, this problem will no longer occur.

STATUS
======

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

Additional query words: kbVBp600bug kbCompiler kbdss kbDSupport kbVBp
======================================================================
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.

Copyright Microsoft Corporation 1998.