Check the search
and the way back.

Explain the core flow

Enter Find mode → set the Open criterion → perform the find → sort by due date. Explain where saving, capturing the find error and handling no matches fit around this flow.

Build and compare

• Preserve your saved Lesson 1 file and records.
• Two controllers and two UI scripts, hidden from the Scripts menu.
• Browse/layout guard and validated commit before entering Find mode.
• Pause off; exact Open criterion; Perform Find without stored requests.
• Capture the find error immediately; distinguish 401 from other errors.
• Sort DueDate ascending, then Task ascending.
• Open tasks and All tasks in the Header, anchored left and top.

Test your working copy

1. On Follow-up Overview in List View, click All tasks. Compare the toolbar and summary counts with your actual tasks. Check ascending DueDate order, then Task order for equal dates.
2. Click Open tasks. Every displayed task should have Status Open; Done tasks disappear from this found set. In the supplied four-task data, the expected result is Alex Morgan’s “Send project outline,” unless you have changed those records.
3. Click All tasks again. Confirm the Done tasks return with their original statuses. Repeat both actions; no new records should appear.
4. In a disposable practice copy, set every task to Done and commit. Click Open tasks. Expect the no-matches message and an empty found set. Dismiss it and click All tasks; every task must return. Discard this practice copy afterward.
5. In a practice copy, clear an existing task’s required Task text, then click Open tasks. Expect a save/validation message before Find mode. Restore its description and commit. Try the search again.
6. Find Open tasks, click Report and check that the report contains that found set. Exit Preview if needed, then Back to Tasks. Click All tasks before making a report of everything.
7. Resize the window and check that all five Header buttons remain readable and anchored left. Save, close and reopen; confirm the controls and original records remain. Rerun each search after opening.

Explain the behavior

Why would the same Set Field criterion be dangerous in Browse mode?

How does an empty found set differ from an empty table?

Why must you rerun Open tasks after changing statuses?

Your notes and questions