I understand what you are getting at, Peter.

But given that a wish list item has to stick to a single wish, I feel that it is safer to omit AERROR() from this discussion.

IF it ended up that AERROR() was also improved as a result of this wish, then I surely would not complain < s >.
Conversely, though, if there ended up being a worry of breaking existing code that currently employs AERROR(), then this wish might be dismissed outright and that certainly is not what I want.

The assumption that AERROR() uses the same messages might also be incorrect.

I invite you to make a wish regarding improvements to AERROR(). There might also be more things that can be improved there than simply the message text.

I hope you see my point.
Thanks

>Jim,
>
>The default texts are similar to, or even equal to, or even derived from, ERROR(). Which is repeated in the AERROR() array, element 2. In development mode one may prefer the default messages, but the enduser will always (always?) see a code generated error message that probably uses AERROR(). IMHO, this discussion should also be about AERROR(). Improvements that are limited to the default error message text are only halfway improvements.
>
>>Peter,
>>
>>What I'm after is improvements in error message TEXT as it appears in the messagebox and improvements to the content of the Help detail text.
>>
>>I leave changes to AERROR() or other stuff to other people.
>>
>>cheers
>>
>>>Jim,
>>>
>>>Are you only referring to the text in the default error message box? I guess not.
>>>
>>>Do you want the vfp-team to upgrade the error() texts themselves, or do you want them to upgrade the array texts as created by AERROR()? Or do you even perhaps propose a new array?