BUG: Norton Desktop 3.0 May Crash Visual Basic

 Last reviewed: May 16, 1996
Article ID: Q142248
The information in this article applies to:
  • Professional and Enterprise Editions of Microsoft Visual Basic for Windows, 16-bit only, version 4.0

SYMPTOMS

When the FileAssist option in Norton Desktop 3.0 is enabled, using certain commands in the File menu of your 16-bit Visual Basic application may cause Visual Basic to crash before appropriate dialog box appears. The following are the File menu commands that may cause this problem.

  • Open Project
  • Save File As
  • Save Project As
  • Add File

This behavior occurs in both design mode and compiled programs.

CAUSE

The FileAssist's configuration changes the Common Dialogs displayed by Visual Basic so that the Common Dialogs appear in 3D. The problem appears to be caused by a conflict with the inherent 3D effect exhibited by the default Common Dialogs.

RESOLUTION

There are three resolutions to this problem.

  • Uninstall Norton Desktop from your system.

    -or-

  • Add the following entry to the compatibility section of the File Assist initialization file (FASSIST.INI) of both Norton Desktop and your compiled program. 

          [Compatibility]
      vb=0x00df

    The entry removes the 3D effect from the Common Dialog control called by Visual Basic 4.0 and eliminates the conflict.

    -or-

    In Norton Desktop's configuration settings, disable FileAssist.

Additional reference words: 4.00 vb4win vb416
KBCategory: kbbuglist kb3rdparty
KBSubcategory: IAPThird

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