InstantForum 2017-1 FinalStrataFrame Forumhttp://forum.strataframe.net/StrataFrame ForumTue, 09 Jun 2026 20:53:12 GMT20http://forum.strataframe.net/FindPost4007.aspxI'd like to provide my users with an error message if they enter an invalid value into a bound control and also prevent them from leaving that control until the entry is corrected.&nbsp; I'd like to keep all of the business rules in the business object rather than in the control's Validating event.&nbsp; Do you guys have any guidance as to how this can best be accomplished?</P><P>Another common situation for us is that the entry of one field will cause one or more other fields to change their value.&nbsp; Is having the business object sink its own FieldPropertyChanged event the best way to handle that?</P><P>Thanks for your help.</P><P>Fran Parker</P><P>MaxQ Technologies, Inc.Tue, 31 Oct 2006 14:30:48 GMTfparkerhttp://forum.strataframe.net/FindPost4008.aspx[quote]I'd like to keep all of the business rules in the business object rather than in the control's Validating event.&nbsp; Do you guys have any guidance as to how this can best be accomplished?[/quote] <P>This kindof becomes a "sticky wicket" when you start trying to do this.&nbsp; The only way to prevent forward (or backward) navigation in a text box is in the validating event.&nbsp; You can prevent records from being saved, navigated, etc.&nbsp; But the only option .NET even provides in this arena is the validating event.&nbsp; If this type of entry can be avoided, then this is my recommendation.&nbsp; This is what we used to do in our medical system and this is where we got the most complaints.&nbsp; Our users despised it because they would either get stuck or they would keep clicking save and get another error no knowing where the end was.&nbsp; Sorry :ermm: no great revelations here for you.</P><P>[quote]Is having the business object sink its own FieldPropertyChanged event the best way to handle that?[/quote]</P><P>You can go either way here.&nbsp; Generally, standards indicate that if you are changing values on a form, you set the form controls.&nbsp; But if you are changing data, you change the BO field properties.&nbsp; But it really doesn't matter.&nbsp; If you change the field properties of the BO, you may need to call the Refresh of the BO to reflect the changes made to the data:</P><P>MyBO.Refresh("MyFieldName")Tue, 31 Oct 2006 14:30:48 GMTTrent L. Taylor