Time for a quick Access forms quiz. This one covers opening related records, pulling values from open forms, continuous-form labels, and one very important detail: making sure a new parent record is saved before you try to add its child records. See if you can get all five before checking the answers.
Give yourself a few seconds for each question. If you need more time, pause the video. No shame in that. Access forms can be wonderfully useful, right up until an unsaved customer record sends your related contact form wandering off into the laboratory unsupervised.
Question 1: What should an Access command button configured to open a related ContactF from CustomerF normally do?
A. Open every contact record with no filter
B. Open only contacts whose CustomerID matches the current customer
C. Copy all contact records into CustomerT
D. Create a new table relationship each time it is clicked
Answer: B. The button should open only the contacts whose CustomerID matches the CustomerID on the customer currently displayed in CustomerF. The whole point is to show that customer's contacts, not make the user search through contacts belonging to every customer in the database. The table relationship already exists. You do not need to rebuild it every time someone clicks a button. That would be a bit dramatic.
Question 2: Which expression correctly retrieves the value of CustomerID from an open form named CustomerF?
A. =CustomerF!CustomerID
B. =Forms!CustomerID!CustomerF
C. =Forms!CustomerF!CustomerID
D. =Forms!CustomerF_CustomerID
Answer: C, =Forms!CustomerF!CustomerID. The Forms collection represents forms that are currently open. You specify the form name first, then the control name whose value you want. If your form or control names contain spaces, use brackets, such as Forms![Customer F]![Customer ID]. Of course, avoiding spaces in object and control names makes life easier, but that particular horse left the barn in a lot of older databases.
Question 3: What condition is required for a Default Value expression to read a control from another form with the Forms collection?
A. The source form must be open
B. The source form must be in Design View
C. Both forms must use the same record source
D. The source control must be an AutoNumber field
Answer: A. The source form must be open. Access can only retrieve a value with an expression like Forms!CustomerF!CustomerID if CustomerF is currently loaded. If someone opens the contact form directly instead of opening it from the customer form, there may be no open customer form from which to retrieve the default CustomerID.
Question 4: In a Continuous Forms view, where should you place column labels so they appear once above the repeating records?
A. In the Detail section
B. In the Form Footer
C. In a bound text box
D. In the Form Header
Answer: D, in the Form Header. Controls in the Detail section repeat once for every record. That is exactly what you want for fields like FirstName, LastName, Phone, and Email. Labels that should appear only once, like column headings, belong in the Form Header. Putting them in Detail means every record gets its own copy, which is not a heading. It is just visual clutter with ambitions.
Question 5: A user enters a new customer, and the record selector shows the pencil icon. Before opening a form to add that customer's related contact, what should happen?
A. Refresh only the contact form
B. Save or commit the customer record
C. Use DLookup to retrieve the new CustomerID
D. Change CustomerID to a Short Text field
Answer: B. Save or commit the customer record first. The pencil icon means the current record is dirty, meaning it has been edited or entered but has not yet been saved. Until Access commits that customer record, an AutoNumber CustomerID may not be available for the related contact record. Save the parent first, then open the child form and pass along the CustomerID.
How did you do? Five out of five earns you Director of the Facility Beneath the Facility. Missed a couple? No worries. These are exactly the sorts of little form details that separate a database that mostly works from one that behaves properly when real people start clicking buttons.
Watch the embedded quiz video for the full questions and answers, and if you want to go deeper into passing values between forms, filtered related forms, default values, and parent-child record handling, check out Access Expert Level 2, Lesson 4.
Live long and prosper,
RR
No comments:
Post a Comment