More clues. It is definitely a case of base tables vs. views. If the field rule is in the base only , the errorFieldRule works. If the field rule is in the updatebable view (or in both) ErrorFieldRule simply cannot handlie it. forcing the Obehavior.CerrorTable to the proper value does not complete solve the problem either. If we do this it makes through the error routine ok, giving a message, etc. But then it returns back to the save, and instead of rollback the transaction it tries to continue the save, running into a nesting error. I really need help on this one. I have not been able to code a decent solution. It is definitely not a version problem; this occurs in all versions of the framework.

Thanks

Gar