I'm binding an ErrorProvider object to a dataset by calling
ErrorProvider.BindToDataAndErrors() in a WinForms app. That seems to be
working fine.

The only issue I've found is that the error string displayed by an
ErrorProvider has the name of the column prepended to it. That could confuse
users.

The list of error strings for a given DataRow does not have the name
prepended. So it looks like a "feature" of the ErrorProvider class. Deriving
from the class won't solve the problem since the GetError method is not
virtual.

Has anyone seen this too? Do you know of a way to prevent it?

Thanks for any help.

Re: ErrorProvider question by ScaveMail

ScaveMail
Mon Nov 08 16:45:01 CST 2004

Hi,

I have also noticed this "feature". They may say it's by design but
the idea of providing a terse column name for a friendly error
message, without allowing for configuration, is a bug.

Please provide a workaround if there's one available.


Larry Fix <LarryFix@discussions.microsoft.com> wrote in message news:<1E8E33BB-4838-45DC-BE6A-81EF51089187@microsoft.com>...
> I'm binding an ErrorProvider object to a dataset by calling
> ErrorProvider.BindToDataAndErrors() in a WinForms app. That seems to be
> working fine.
>
> The only issue I've found is that the error string displayed by an
> ErrorProvider has the name of the column prepended to it. That could confuse
> users.
>
> The list of error strings for a given DataRow does not have the name
> prepended. So it looks like a "feature" of the ErrorProvider class. Deriving
> from the class won't solve the problem since the GetError method is not
> virtual.
>
> Has anyone seen this too? Do you know of a way to prevent it?
>
> Thanks for any help.