PRB: Syntax Error If VB CDK Custom Property Name Starts w/ Num (78399)

The information in this article applies to:

Microsoft Visual Basic Standard Edition for Windows 2.0
Microsoft Visual Basic Professional Edition for Windows 2.0
Microsoft Visual Basic Standard Edition for Windows 1.0

This article was previously published under Q78399

SYMPTOMS

When a control property starts with a numeric value, Visual Basic generates this syntax error:

Expected: end-of-statement.

However, the property works correctly in the Visual Basic design mode from the Properties bar (or window in version 2.0).

CAUSE

The Property Name (npszName) field in the PROPINFO structure for the Visual Basic Control Development Kit (CDK) cannot start with a numeric value.

RESOLUTION

This information needs to be added to page 143 of the "Microsoft Visual Basic: Control Development Guide" shipped with Microsoft Professional Toolkit for Visual Basic 1.0 for Windows, or page 132 of the "Microsoft Visual Basic: Control Development Guide" shipped with the earlier CDK add-on for Microsoft Visual Basic.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

Rebuild the Circle3 example provided with the CDK after changing the PROPINFO Property_FlashColor structure in CIRCLE3.H to the following:

   PROPINFO Property_FlashColor =
   {
   "2FlashColor", DT_COLOR | PF_fGetData | PF_fSetData |
   PF_fSaveData | PF_fEditable, OFFSETIN(CIRCLE,
   FlashColor)
   } ;

While in Visual Basic development environment (VB.EXE) with the Circle3 control loaded, assign the 2FlashColor property a value:
```
      Circle1.2FlashColor = 2
						
```
Press F5 to generate the "Expected: end-of-statement" error message. The text "FlashColor" will be selected for the syntax error.

Modification Type:	Major	Last Reviewed:	11/18/2003
Keywords:	kbprb KB78399