I have the following code in the error method of my base business class from which all my business classes are derived


LPARAMETERS nerror,cmethod,nline,tcsys16,toerrobj
DO CASE
CASE nerror=1539 && trigger faild
THIS.ErrorTrigger()
CASE nerror=1502 && record in use
This.ErrorUpdateConflict()
CASE nerror=1581 && null in non nullable field
THIS.ErrorFieldRule()
CASE nerror=1526 OR nerror=1541 && connectivity error
THIS.ErrorConectivityError()
CASE nerror=1582 && field rule violate
THIS.ErrorFieldRule()
CASE nerror=1583 && record rule violate
THIS.ErrorRecordRule()
CASE nerror=1585 && update conflic
This.ErrorUpdateConflict()
CASE nerror=1595 && multi_update conflict
This.ErrorUpdateConflict()
CASE nerror=1884 && UNIQUENESS VIOLATED
THIS.ErrorUniqueIndexViolated()
OTHERWISE
RETURN DODEFAULT(nerror,cmethod,nline,tcsys16,toerrobj)
ENDCASE


Since the upgrade to 6.0a all of the above "handled" errors produce an unrecoverable failure. For instance, failure of a "field rule violation" produces the following error on save:

Error # 11
Function, argument, value , type or count is invalid.

Line 89
Code lcMessage=StrTran(DBGETPROP(lcUpdateName,"FIELD","RULETEXT"),"","")
method errorfieldrule

I'd trace it in the debugger, but get shoved into some sort of endless loop every time I try to step out. Before I start sticking "Set Step on" in "errorfieldrule" method, any obvious problems occur to anybody? It the fact that this worked in 4.2 any type of clue?

Thanks