======================================================================
  Microsoft(R) Product Support Services Application Note (Text File)
                BV0700: TROUBLESHOOTING COMMON PROBLEMS
======================================================================
                                                  Revision Date: 11/92
                                                      No Disk Included

The following information applies to Microsoft Visual Basic(TM) for
Windows(TM) versions 1.0 and 2.0.

 --------------------------------------------------------------------
| INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY    |
| ACCOMPANY THIS DOCUMENT (collectively referred to as an            |
| Application Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY      |
| KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO    |
| THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A     |
| PARTICULAR PURPOSE. The user assumes the entire risk as to the     |
| accuracy and the use of this Application Note. This Application    |
| Note may be copied and distributed subject to the following        |
| conditions: 1) All text must be copied without modification and    |
| all pages must be included; 2) If software is included, all files  |
| on the disk(s) must be copied without modification [the MS-DOS(R)  |
| utility DISKCOPY is appropriate for this purpose]; 3) All          |
| components of this Application Note must be distributed together;  |
| and 4) This Application Note may not be distributed for profit.    |
|                                                                    |
| Copyright 1992 Microsoft Corporation. All Rights Reserved.         |
| Microsoft and MS-DOS are registered trademarks and Visual Basic    |
| and Windows are trademarks of Microsoft Corporation.               |
 --------------------------------------------------------------------

1. Q. When I attempt to load a Visual Basic version 1.0
      application into version 2.0 of Microsoft Visual Basic for
      Windows, I receive the error message "Form name is a class name."
      What is causing this error?

   A. With version 2.0 of Visual Basic, you cannot have a form name
      that is identical to a form, control, or object class name. For
      example, invalid form names include "form", "list box", "text
      box", "printer", "app", "database", and "dynaset". The form name
      also cannot be the same as the class name of any custom control
      that appears in the project. To work around this error, you must
      load the form into Visual Basic version 1.0 and change the form
      name. If you have already installed version 2.0 over version 1.0,
      you must copy the VB.EXE file from your version 1.0 distribution
      disks. To do this, you can either run the version 1.0 Setup
      program again or use the Windows EXPAND utility to copy the
      VB.EXE file from the original distribution disks.