BUG: Duplicate Procedure Name Alters Original Capitalization

ID: Q76514

The information in this article applies to:

Microsoft Visual Basic Standard and Professional Editions for Windows, versions 2.0, 3.0
Microsoft Visual Basic programming system for Windows, version 1.0

SYMPTOMS

If you enter a Sub statement with a procedure name that duplicates an existing procedure name in spelling but not in capitalization, you will receive a "duplicate definition" error message, but the original procedure name will be changed to match the new capitalization. This also happens if you choose New Procedure from the Code menu and enter a duplicate name.

STATUS

Microsoft has confirmed this to be a bug in Visual Basic versions 1.0, 2.0, and 3.0 for Windows. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

If you choose the OK button after receiving the "duplicate definition" error message, the old name of the subroutine will be updated to show the changes in capitalization, even though there was a "duplicate definition" message.

Steps to Reproduce Problem

Method 1

Within a module, create a Sub procedure called "a".

From the Code menu, choose New Procedure. Name the procedure "A" and choose the OK button when the "duplicate definition" message is displayed.

Method 2

Within a module, create a Sub procedure called "a".

Within the same module, create a Sub named "A" and choose the OK button when the "duplicate definition" message is displayed.

The original procedure name is updated with the most recent Sub procedure name taking the place of the old Sub procedure name, despite the "duplicate definition" error message. To work around the problem, change the capitalization.

Additional query words: buglist1.00 buglist2.00 buglist3.00 2.00 3.00

Keywords :
Version : WINDOWS:1.0,2.0,3.0
Platform : WINDOWS
Issue type :