I think I may have found a problem in VFP5.0 - anybody else experiencing this or am I hallucinating:

When a field level validation clause in the DBC fails I have an error handler to display information and 'correct' the problem. Part of this is the use AERROR to load the error information into an array. When I run this under VFP 5.0 both positions 2 and 3 in the array contain the error text. Under 3.0 it held the name of the field the error occurred on. Since it can't get the field name, the error handler crashes and burns. Not good.

I still have 3.0 installed so I went back and reviewed. Yep it works there. I also tried with tables converted from 3.0 and created under 5.0 - same results. SYS(2018) also returns the same thing (the message text - NOT the parameter. Am I missing something here??