Home > Articles > Programming > Windows Programming

This chapter is from the book

21.9 Creating a Master/Detail View Application

The previous examples demonstrated using LINQ to SQL to combine data from different tables and displaying data from a database in a GUI. It is often necessary to combine the two, as the example in this section does. Figure 21.28 demonstrates a master/detail view—one part of the interface (the master) allows you to select an entry, and another part (the details) displays detailed information about that entry. In this example, you select either a book title or an author, and the details displayed are the co-authors of the book or the titles the author has written, respectively.

Fig. 21.28 Using a DataGridView to display details based on a selection.

 1  // Fig. 21.28: MasterDetailForm.cs
 2  // Using a DataGridView to display details based on a selection.
 3  using System;
 4  using System.Linq;
 5  using System.Windows.Forms;
 6
 7  namespace MasterDetail
 8  {
 9     public partial class MasterDetailForm : Form
10     {
11        public MasterDetailForm()
12        {
13           InitializeComponent();
14        } // end constructor
15
16        // connection to database
17        private BooksDataContext database = new BooksDataContext();
18
19        // this class helps us display each author's first
20        // and last name in the authors drop-down list
21        private class AuthorBinding
22        {
23           public Author Author { get; set; } // contained Author object
24           public string Name { get; set; } // author's full name
25        } // end class AuthorBinding
26
27        // initialize data sources when the Form is loaded
28        private void MasterDetailForm_Load( object sender, EventArgs e )
29        {
30           // display AuthorBinding.Name
31           authorComboBox.DisplayMember = "Name";
32
33           // set authorComboBox's DataSource to the list of authors
34           authorComboBox.DataSource =
35              from author in database.Authors
36              orderby author.LastName, author.FirstName
37              let name = author.FirstName + " " + author.LastName
38              select new AuthorBinding { Author = author, Name = name };
39
40           // display Title.BookTitle
41           titleComboBox.DisplayMember = "BookTitle";
42
43           // set titleComboBox's DataSource to the list of titles
44           titleComboBox.DataSource =
45              from title in database.Titles
46              orderby title.BookTitle
47              select title;
48
49           // initially, display no "detail" data
50           booksBindingSource.DataSource = null;
51
52           // set the DataSource of the DataGridView to the BindingSource
53           booksDataGridView.DataSource = booksBindingSource;
54        } // end method MasterDetailForm_Load
55
56        // display titles that were co-authored by the selected author
57        private void authorComboBox_SelectedIndexChanged(
58           object sender, EventArgs e )
59        {
60           // get the selected Author object from the ComboBox
61           Author currentAuthor =
62              ( ( AuthorBinding ) authorComboBox.SelectedItem ).Author;
63
64           // set booksBindingSource's DataSource to the
65           // list of titles written by the selected author
66           booksBindingSource.DataSource =
67              from book in currentAuthor.AuthorISBNs
68              select book.Title;
69        } // end method authorComboBox_SelectedIndexChanged
70
71        // display the authors of the selected title
72        private void titleComboBox_SelectedIndexChanged(
73           object sender, EventArgs e )
74        {
75           // get the selected Title object from the ComboBox
76           Title currentTitle = ( Title ) titleComboBox.SelectedItem;
77
78           // set booksBindingSource's DataSource to the
79           // list of authors for the selected title
80           booksBindingSource.DataSource =
81              from book in currentTitle.AuthorISBNs
82              select book.Author;
83        } // end method titleComboBox_SelectedIndexChanged
84     } // end class MasterDetailForm
85  } // end namespace MasterDetail

In the previous examples, the IDE automatically generated the BindingSource, BindingNavigator and GUI elements when you dragged a data source onto the Form. While this works for simple applications, those with more complex operations involve writing more substantial amounts of code. Before explaining the code, we list the steps required to create the interface the code manipulates.

Step 1: Creating the Project

Create a new Windows Forms Application called MasterDetail. Name the source file and class as indicated in Fig. 21.28, and set the Form’s Text property to Master/Detail.

Step 2: Creating LINQ to SQL Classes

Follow the instructions in Section 21.6.1 to add the Books database and create the LINQ to SQL classes to interact with the database.

Step 3: Creating GUI Elements

Add two Labels and two ComboBoxes to the top of the Form. Position them as shown in Fig. 21.29. The Label and ComboBox on the left should be named authorLabel and authorComboBox, respectively. The Label and ComboBox on the right should be named titleLabel and titleComboBox. Set the Text property of the Labels as indicated in the screenshot. Also change the DropDownStyle properties of the ComboBoxes from DropDown to DropDownList.

Figure 21.29

Fig. 21.29 Finished design of MasterDetail application.

Create a DataGridView called booksDataGridView to hold the details that are displayed. Unlike previous examples, do not automatically create it by dragging a data source from the Data Sources window, because this example sets the data source programmatically. Instead, manually add it from the Toolbox. Resize the DataGridView so that it fills the remainder of the Form. Because this control is only for viewing data, set its ReadOnly property to True using the Properties window.

Finally, we need to add a BindingSource named booksBindingSource from the Data section of the Toolbox, to act as an intermediary between booksDataGridView and booksDataContext. As in the previous examples, it does not appear as a visible component on the Form, but appears in the component tray. The BindingSource will be used as a data source for booksDataGridView—we will fill booksBindingSource with data from the Authors or Titles table, depending on which drop-down is selected. With the GUI creation complete, we can now write the code to provide the functionality we require.

The Master/Detail Application

When the code has been written, the Master/Detail application allows the user to select an author or book title from one of two drop-down lists, and view the details of the titles that author worked on or the authors of that book, respectively.

Class MasterDetailForm contains the nested class AuthorBinding (lines 21–25). Class definitions may be nested inside other classes. AuthorBinding is private because it should be accessed only from its containing class. We created the AuthorBinding class to allow us to associate a full Author object—the Author class is automatically generated by LINQ to SQL—with each row in the drop-down list, but have it display the author’s full name. Recall that the author’s name is stored as two separate fields in the database, so the Author class does not have single property that retrieves the full name. The Name property of the AuthorBinding class stores the author’s full name, and the Author property stores the Author object that contains the author’s information from the database.

The ComboBox’s DisplayMember property is set to the String "Name" (line 31), which tells the ComboBox to use the Name property of AuthorBinding to determine what text to display for each AuthorBinding object. Lines 34–38 create an AuthorBinding object for each author and assign it to the authorComboBox’s DataSource property. This makes authorComboBox create one entry per author. Recall from Section 10.17 that object initializers (e.g., line 38) can be used to initialize an object without calling a constructor.

There is no need to create a custom class to wrap the Title class, because it already has a property for what we want to display—the BookTitle property. The text in the ComboBox is set to be retrieved from the BookTitle property (line 41). Lines 44–47 create and assign the DataSource for titleComboBox—a sorted list of Title objects.

Initially, we don’t want to display any data in the DataGridView. However, when the ComboBoxes are created and initialized with their DataSources, their SelectedIndexChanged event handlers are called, setting a DataSource for booksBindingSource (connected to booksDataGridView on line 53). To prevent this, we explicitly set the DataSource property to null (line 50)—this is done before connecting the DataGridView to avoid loading data that will just be thrown away when the DataSource is reset.

Simple GUI elements like ComboBoxes can be populated from a data source—in this case, the result of a LINQ to SQL query. However, the DataGridView is more complex and requires an intermediary class (a BindingSource) as its DataSource. We can change the columns and data displayed in booksDataGridView merely by changing the DataSource property of booksBindingSourcebooksDataGridView will update the data and even column names automatically.

The authorComboBox_SelectedIndexChanged event handler (lines 57–69) performs two distinct operations. First, it retrieves the selected Author (lines 61–62). The ComboBox’s SelectedItem property returns an object, so the SelectedItem property’s value must be cast to the AuthorBinding class we used as the data source. The event handler then accesses the AuthorBinding’s Author property to retrieve the wrapped Author object. Second, the event handler uses LINQ to retrieve the Title objects representing books the Author worked on (lines 67–68)—the mechanism for this was explained in the preceding example. The results of the LINQ query are assigned to the DataSource property of booksBindingSource (line 66)—note that the event handler for authorComboBox sets the DataSource to a data from the Titles table because we want to display Title rows associated with that Author.

The event handler for titleComboBox is structured identically to the authorComboBox one. The primary difference is that the author and title names are switched. Also, the first step is slightly simpler, because the Title class did not need to be wrapped to display correctly in the ComboBox.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020