Article ID: 171819
Article Last Modified on 12/10/2003
APPLIES TO
- Microsoft Visual Basic 5.0 Control Creation Edition
- Microsoft Visual Basic 5.0 Learning Edition
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
This article was previously published under Q171819
SYMPTOMS
Incompatibility Warnings may appear when you are trying to make a project
with binary compatibility even though no subroutine or function declaration
has changed.
CAUSE
If a function declaration contains an optional parameter with a default
value in the declaration that does not use a valid enum, Visual Basic will
define it as a short, which conflicts with the compiled version which is a
long.
RESOLUTION
Install Visual Studio 97 Service Pack 2 or use a valid enumeration in the
Function or Subroutine declaration.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. This bug has been fixed in Visual Studio
97 Service Pack 2.
For more information on the Visual Studio 97 Service Pack 2, please see the
following article in the Microsoft Knowledge Base:
170365
: INFO: Visual Studio 97 Service Packs - What, Where, and Why
For a list of the Visual Basic 5.0 bugs that were fixed in the Visual
Studio 97 Service Pack 2, please see the following article in the Microsoft
Knowledge Base:
171554
: INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2
Additional query words: kbDSupport
Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171819