>>Thanks everyone for the help. What happened was someone placed code in the Error event for the base form. We then removed the code but did not reset it to the default. If we do that it works however when we run some of our forms we get an index order on the base form so then we have been copying the old classes back. Has anyone seen that problem? Thanks
>
>William,
>
>It's not clear, what is the problem, you're now having. Could you please explain it in more details?

Seems to be one of those "why doesn't the parent code fire when the child code is blank", when the child code is not actually absent, it contains one empty line. Just try to insert a carriage return into any object's otherwise empty method, and you'll see that the parent code doesn't fire. As far as Fox is concerned, the method is there, different from its parent's code, and it runs that and not the parent method, even if it has no actual lines.

The above problem of new errors appearing now is not a new problem, and not caused by this. The errors were there before, there was just this empty code in form.error which was hiding them, and now as this empty code was removed, they resurfaced.

I've had this a couple of times, and actually had two difficult weeks when I removed such a piece of error hiding code, when all the small stuff started popping up all over the place.