Umm...
In theory, Nancy, you're absolutely right. However, I haven't been able to get the array to be filled correctly. I posted this about 2 months ago, and no-one else had any better luck. Maybe someone new will know how to make it work.

Barbara

>Hi.
>
>I snipped the following from the help on TABLEUPDATE([nRows [, lForce]] [, cTableAlias | nWorkArea]
>[, cErrorArray])
>
>**
>Unlike the 0 and 1 values for nRow, an error doesn’t occur when a change can not be committed, and Visual FoxPro continues to process any remaining records in the table or cursor. If cErrorArray is included, an array containing error information is created when an error occurs.
>
>The default value for nRows is 0.
>**
>
>I think using nRows = 2 and cerrorArray will get you where you need to be.
>
>HTH
>
>>How can we determine which field has violated the field rule that wehave set in the database. In VFP 3.0 we could use =AERROR(arrayerr)and arrayerr(3) would give us the name of the field, however in VFP 5( good knows why they have changed it!) we get the Message text! andnot the name of the field, infact =AERROR(), SYS(2018) ... don'treturn the name of the field at all!Further the Tastrade application for VFP 5 uses this to trap fieldrule violation - tsbaseform error routine and the coding there wouldgive us a error. Microsoft have not gone thru there own example codeproperly!