>Actually Fred, the AddMode is a TOOLBAR property that came with the txtbutns class from the WIZARD. When I dropped it on my form, I did not have to create any additional properties for the TOOLBAR to work.
>
>Does the .PARENT classification need to be there because the ADD BUTTON is a segment of the TOOLBAR class?
Peter,

Just to clear up your understanding. The add button is NOT in a toolbar. A toolbar is a completely different thing. The add button is in a Container object and that container is the parent of the button.

THIS - refers to the specific object that the code is in (in your case the button)

THISFORM - Refers to the form that the code is in.

Parent (Property) - Refers to the parent object or containing object for the object that the code is in (in your case the container of the button).

In VFP every object has a parent property that is a reference to the object's immediate container.

The reason, in my other message, that I recommend not using the wizstyle classes is that they are designed in a way that makes poor use of the continership and causes convoluted code jumping around the containerships.

The problem with this design approach is this; if you are a very experienced OO programmer with VFP you can navigate and understand the code and how it works. However, as an experienced programmer you would probably be designing your own classes anyway. If you are new to VFP the design of the wizstyle classes is obtuse and confusing and is NOT a good indication of how things should be done. The wizstyle classes canb e used as is and they will function fine, however if you want to alter their behavior, as you did, then you must understand how they work in the first place to know how to change them and they are poorly desinged.