FIX: Visual FoxPro Fails If Subclass Name Ends in a Number
Article ID: 139108
Article Last Modified on 9/30/2003
APPLIES TO
- Microsoft Visual FoxPro 3.0 Standard Edition
- Microsoft Visual FoxPro 3.0b Standard Edition
This article was previously published under Q139108
SYMPTOMS
When you place a subclass of an existing class on a form, and the name of
that subclass ends in a number, Visual FoxPro fails and returns this error
message:
A member object with this name already exists.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article. This problem has been fixed in
Visual FoxPro 5.0 for Windows.
Additional query words: class member object
Keywords: kbbug kbfix kbvfp500fix KB139108