The Upgrade Wizard cannot help you, other than highlighting the problem in the upgrade report. If you have used an incorrect constant, you will need to fix it on your own. Current = vbNormal ' The same underlying value 'UPGRADE_WARNING: VB.Screen property Screen.MousePointer has a 'new behavior. 'UPGRADE_WARNING: VB.Screen property Screen.MousePointer has a 'new behavior. 'UPGRADE_ISSUE: VB.Screen property Screen.MousePointer does not 'support custom mousepointers. Current = _ .Default ' Incorrect constant, same underlying value 'UPGRADE_ISSUE: Unable to determine which constant to upgrade 'vbNormal to. ' Correct MousePointer constant 'UPGRADE_WARNING: VB.Screen property Screen.MousePointer has a 'new behavior.

The following results from the Upgrade Wizard illustrate this scenario: On the other hand, the Upgrade Wizard can work with an underlying constant, if used, and can translate it to a proper constant in Visual Basic. When you upgrade your project, however, the Upgrade Wizard will not be able to upgrade the vbNormal constant because it is not defined for the MousePointer and you will be left with an upgrade warning and a compile error.

' Correct MousePointer constant Screen.MousePointer = vbDefault ' Incorrect constant, same underlying value Screen.MousePointer = vbNormal ' The same underlying value Screen.MousePointer = 0 The following example from Visual Basic 6 demonstrates three equivalent statements that work just fine: It is also fairly common for developers to use the underlying values for constants. Constants such as vbNormal are frequently used in place of vbDefault (a proper constant for the MousePointer property). The most common example of the use of bad constants is in relation to the Screen.MousePointer property. NET is more strict and requires the correct enumeration constants because enumerations are now actual types, not just collections of friendly names for integers.

Unfortunately, this arrangement allows developers to use constants intended for different purposes interchangeably and also to use simple integers (representing the underlying values) in place of the constants. Because enumerations in Visual Basic 6 represent integer values instead of distinct types, the process can verify only their underlying values. Each member of the enumeration is assigned an integer value in code, the member name evaluates to its assigned integer. In Visual Basic 6, you can create a set of named constants, known as an enumeration.

Vb6 custom mouse pointer