Viv,

I'm not sure what was going on--very unusual. It was the only form in the sample application that displayed this behavior--and oddly enough, if you closed the form, rather than navigate to a new record, it did display the warning. I simply rebuilt the form, and it worked correctly--another Windows Forms mystery!

I have uploaded a hot-fixed version of MM .NET 2.4 that contains this update.

Best Regards,