Create projects
for the right contact.

Build and compare

• Back up the saved, closed Course 3 file.
• Projects: five default fields plus ContactID and ProjectName, both Text.
• Require ProjectName; keep names and ContactID non-unique.
• Contacts::PrimaryKey = Projects::ContactID; related creation on Projects only; cascade deletion off.
• Duplicate Contact Notes as Contact Projects; base table Contacts, portal Projects, row field Projects::ProjectName.

Try it yourself

1. Use a disposable working copy. Open Contact Projects in Browse mode, Form View. If only one contact is found, use Show All. Find Alex Rivera by last name or email, not first name alone. Note the Contacts record count.
2. In the portal’s blank row, enter Website refresh. Click outside the fields to commit. Enter Autumn workshop in the next blank row and commit.
3. Switch to Alex Morgan. Rivera’s projects should not appear. Create another project named Website refresh for Morgan. The repeated name is intentional: it must remain a separate project.
4. Switch between Rivera and Morgan. Expect two projects for Rivera and one for Morgan. The contact count must not increase. The blank portal row is an entry space, not an additional saved project.
5. On a disposable copy, clear an existing project’s name and try to commit. Expect required-value validation. Restore its name and commit; do not override validation.
6. Open Contact Task Views, Follow-up Overview and Follow-up Report using the Layout menu. Check that existing tasks, statuses, navigation and report return still work. No task has been assigned to a project yet.
7. Save and close the file. Reopen Contact Projects and verify the two contact-specific project lists persist. Keep this saved working file for Lesson 2.

Explain what you learned

Why can ContactID repeat while Projects::PrimaryKey stays unique?

Why does the toolbar’s New Record create a contact here?

What proves the two Website refresh projects are separate and saved?

Your notes and questions