Ok, I understand what you're saying, and I've done that...pretty much, but what about the wierd data stuff...how the actuall data isn't being edited, but the program thinks it is...is there a data cache or something that I should be clearing?

>If there is any code in the error method, that error method wil be the only one to fire. It will not automatically pass the error along to anyparent objects or an ON ERROR routine. What is happening is, this routine is catching the error and not doing a thing about it. If you want to bypass this error method, empty it, or better yet, have it call your ON ERROR method with the parameters it needs. (unless you just want to see the VFP error box)...
>
>
>>Thanks for the post Eric =)
>>
>>Well, for one thing, I said "toolbar" in my post, it's acutally a wizard button group, with back, forward, top, bottom, find, print, exit...etc.
>>
>>Anyway, I "disabled" the error handling in the parent class by putting a coment in the child class(the button group I'm using in my form)...that should make VFP look at my comment and not the original code right? Well, in this case though, even if I reset that event, it still acts as below. =(
>>
>>>I have a version of my program that has data on a server...I'm working on trapping a #1104 error to see if I can do something about it, or at least learn more about this troublesome error...however, in order for me to do this, I need to recreate #1104 conditions, the best way(I thought) to do this was to accesst the data, then disconnect the network cable and then hit navigation buttons...which works...until I put in a little more code to trap this error. In my app I'm using a wizard toolbar, which has it's own error handler in the Error Event. Well, I thought I'd try and dissable that and make it use my own that gave more info...MISTAKE!! after doing this, I'll start the program, disconnect from the network...and NO ERROR!?!?! I CAN EVEN CHANGE DATA, SAVE IT CLOSE THE PROGRAM...RECONNECT AND THE RE-OPEN THE PROGRAM AND THE
>> DATA IS STILL CHANGED...BUT THE ACTUAL DATA IS NOT CHANGED?!?!? ARGH!!!! This is nuts...well it's friday, so screw it!!
>>
>>>It sounds like some error handler is handling the error and not doing anything about it. How did you "disable" the toolbar's error method?