Sub Main() doesn't exist

Sub Main is designated as the Startup Object in the Project Properties dialog, however, the current project doesn't have a Sub procedure named Main in any module.

• Sub Main was created in a Form or Class module, instead of in a standard module.

  Add a standard module to the project, and in that module create a Sub procedure named Main.

• The project was created as a Visual Basic 4.0 OLE server (that is, it had at least one class module whose Public property was True) and a form was designated as its Startup Object.

  A form should not be used as the startup object of a component (see “Starting and Ending a Component,” in “General Principles of Component Design” in the Component Tools Guide). Visual Basic 4.0 could not prevent forms as startup objects of components (OLE servers).

  Later versions of Visual Basic correct this problem. When loading a project that has both a public class and a form that's been designated as the Startup Object, Visual Basic designates Sub Main as the Startup Object instead. The resulting error message alerts the user to the change.

  If you wish to show a form when your component starts, you can do so from Sub Main. It is recommended that you do so only if your program is an EXE project, and is starting because the user selected it from the Startup menu or from the Windows Explorer. You can detect this by testing App.StartMode at the beginning of Sub Main.