We don't currently have a need for this in our applications. We've had the functionality in the past, but we never used it, and anything we didn't use, we pulled, because it was unneeded overhead. If you can find a convincing reason to add it, we might put it in Currently, if you wanted to implement some type of warning, you could add a collection to the business object you want the warnings on. Then, in the BeforeSaveEvent, you could show a popup to the end-user asking them if they are sure they want to save the record. As for using the ErrorProvider with a different icon, you could add that in the AfterSaveEvent handler.



Let me know what you think...

I guess there are a couple of way it could be done.  I was thinking of something like the error messages with a "warning" or "information" icon that would provide the user with the message.

I would think that simply showing these warning icons after the save would require the least amout of changes to the framework as aposed to messaging the user before the save takes place.

Do you have a need for something like this in the applications that you are developing?

Scott

Are you thinking of more functionality than just storing off the message? Like displaying a warning to the end user before they save?

I have a rule that really should not stop the saving process, like using the addbrokenrule call would do.  How would you suggest taking care of this type of issue?  How about a warnings collection and an addwarning call?

Just a thought.