skip to content »

Tab control validating

Each tab would have its own button, and if a button on a tab is pressed, only the controls on that tab should be validated. NET validation controls into the different Tab Panels, a click on a button will validate all of them.This is use case 1, where you want to validate all user input at once.

tab control validating-51tab control validating-88tab control validating-87tab control validating-67

Others, however, have special needs that Outlook 2013 does not address, perhaps because of the way these organizations do business or because of specific requirements in their particular industries.The solution for use case 1 is to insert a Validation Summary next to the submit button, outside of the Tab Container. Each validation control has a property Validation Group. The button on each tab should have its Validation Group property set to the same value as the validation controls on that tab.The Validation Summary can alert the user to validation errors across all tabs. In the button's click event handler, be sure to call the page's Validate method with the validation group as a parameter, before checking Page. One more thing to note about user input in the Tab Container: There is a bug in the Tab Container which resets the active tab if you have a control on a tab with Auto Post Back set to true.With either strategy, it’s important to remember that you’re programming events that are specifically associated with the item involved, not with the Outlook 2013 application generally.In other words, when you put code behind your form, you’re dealing with events related to the item that’s represented by the form.Whatever your situation, you can easily make changes to the existing Outlook 2013 forms, or you can even design new ones.

The changes you make can be simple or complex: You might add one or two fields to the standard contact form, or you might add a considerable amount of program code to allow Outlook 2013 to perform custom tasks or interact with other Microsoft Office 2013 system applications.

To work around this issue, set the Tab Container's Active Tab property in the handler of the autopostback event.

EVEN without any custom programming, Microsoft Outlook 2013 provides an excellent set of features.

This is because in form development, you can access only the events associated with the item in question.

Outlook 2013 uses a combination of forms, item types, and message classes as its fundamental components.

Forms are such a normal part of everything we do on computers that we sometimes take them for granted.