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?



>>Found it... don't understand why, but found it....
>>
>>Should be THIS.PARENT.ADDMODE
>
>I believe you had said that AddMode was a form property? Since this code is in the button click, you could reference a form property via this.Parent.AddMode, but the more correct way would be thisform.AddMode.
>To explain why the above needs Parent, is that the button is in a form (a container) and .Parent is a way to reference the container of an object. When you get into grids, you'll probably find a use where you must use .Parent to reference things.
>
>
>>
>>That triggered some sort of error in the processing routine for the DODEFAULT that caused all the code to continue to be cancelled and the database to be reverted.
>>
>>
>>
>>
>>>I think that's what I am going to try next as well although as a relatively new VFP programmer, I've never stepped through a VFP app before. I have on 'C' apps so I understand the concept. I'm going to see what happens with and without those lines commented and compare it.
>>>
>>>
>>>>>Dan,
>>>>>
>>>>>After the MessageBox cleared, the WAIT WINDOW box showed up. Once I cleared that, nothing changed on the form like it should have.
>>>>>
>>>>>
>>>>>
>>>>>>>Dan,
>>>>>>>
>>>>>>>Tried that, didn't work. The THIS.ENDIF is just a property on the toolbar that is .T. or .F.
>>>>>>>
>>>>>>
>>>>>>Odd. Try adding any line of code prior to the dodefault()
>>>>>>WAIT WINDOW "Before DODEFAULT"
>>>>
>>>>I would definitely step through. You said this was wizard buttons correct? Maybe somethings happening to the _SCREEN.ActiveForm. Just a guess.