Hi Sonali,

Yes they did change this in VFP 5. Unfortunately this is there in VFP6 too.

The only way I can think of is using AFIELDS() to get all the information of the current alias into an array and locate the right error message. I sincerly hope there is a better way to achieve this.

>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!