Kevin

I have been side tracked with some other issues and am now getting back to my MM stuff.

the answer is that I double checked and both DisplayErrorProvided and DisplayErrorDialog are checked in the windows property screen. I got the sample project "Order System WPF C#" supplied with MM to run and it acts the same way. That is the message window will come up with all the broken rules listed, but there is no field indicator - red circle, also when you hover the mouse there is also no broken rule message. As a further test I got the sample application "MM Northwind Sample Application" running and the borken rules indicators do work, get the message box, icon at end of the field, and message when hover mouse over icon.

an aside if I can get on my soap box for a while. when I was doing my testing trying to even get the broken rules to fire, I was pulling out what little hair I had until I discovered that I was being mislead by the function mmType.IsEmpty(), I couldn't figure out why it didn't fire until I discovered that it is really misnamed. It is not accually an isempty function, it is really an isnull function. to get the rules to trigger reliably I had to do a trim on the strings I was passing to it. end of soap box.

didn't get time yet to see if I get the cancel exception in the sample application.
another aside, in both the WPF project that I created from the jump start instructions and the sample WPF application, when you are in the order window and click on the close button on the list window, not only does it close the orders windows, it closes the main window as well but you are still running in debug mode and have to do a stop debug to get back to design mode.