Title: Entering Data in the Associative Entity Table of a M:M or Ternary Relationship
1Entering Data in the Associative Entity Table of
a MM or Ternary Relationship
- If you came to this presentation via a web
browser, - right-click and choose Full Screen before
proceeding. - Click mouse or press space bar to continue.
- This presentation was prepared by Professor Steve
Ross, with the advice of other MIS Faculty, for
use in MIS Classes at Western Washington
University. Please contact Dr. Ross for
permission to use in other settings..
2The Challenge
- Create a form for the entry of worker
assignments, to include the foreign keys for
WorkerID and BuildingID - Information about both buildings and workers must
be entered prior to use of this form
3Step 1 Source Data
- Create a view containing the data for the form
- Normally, the view is based on a single table
- vueFrmAssignment contains all fields of
tblAssignment - Determine field and control characteristics
4Step 2 Layout
- Create a draft view of the form, giving
approximate placement and type of controls for
each data item
I usually do this by hand, not in a graphic
program such as this
Standard Form Heading
Person Building Start Date
Person list combo box
Building list combo box
StartDate
These will be combo boxes, bound to the relevant
fields but displaying data from the related tables
These will be a text box bound to the relevant
field
5Step 3 Create Version 1
- Use the view created in Step 1 as the record
source for the form - Depending on your production environment
- Use application generator to create form
- Create form from a design master
- Add all desired fields to the form
6Step 4 Fine Tuning
- Convert text boxes to combo boxes or other
controls as necessary. - Apply check constraints and other properties to
controls. - Once controls are set, apply other design
standards.
See this presentation for discussion of
technique. The form illustrated met MIS 421
design standards when it was created. Subsequent
changes to the standards may have occurred.
7Step 5 Quality Assurance
- Can the user change data in an existing record?
- Can the user enter new records?
- Are all constraints working properly? (Test the
limits.) - Have all Design Standards been met?