BUG: Ambiguous Name Detection for Private Functions Named "Main"


When a Visual Basic project contains two or more functions named "Main" (but only one is Public) and Sub Main is set as the Startup Object, the following error is received when the Project is compiled or run:
"Ambiguous name detected: main"


In addition to Public functions, Visual Basic also searches for Private functions for any name conflict.


Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

More Information

Steps to Reproduce Behavior

  1. Create a new Standard EXE project in Visual Basic. Form1 is created by default.
  2. Select Project Properties from the Project menu.
  3. Change the Startup Object to Sub Main.
  4. Add two code modules to the Project by choosing Add Module from the Project menu twice.
  5. Paste the following code in the code window of Module1:
          Public Sub Main
    Msgbox "Hello"
    End Sub
  6. Paste the following code in the code window of Module2:
          Private Sub Main
    Msgbox "Hi"
    End Sub
  7. Press the F5 key to run the project. Note that the following error message is received:
    "Ambiguous name detected: main"

Id. de artículo: 191693 - Última revisión: 05/13/2003 - Revisión: 1