7.3.9 Database Design In Microsoft Access Apr 2026

She looked at the Excel monster. It had a column DonorName repeated next to every donation. If a donor changed their address, she had to update 50 rows. Chaos.

That night, alone in the fluorescent glow of her cubicle, Elara opened Access 365. She stared at the blank screen. On the printout, Marcus had scrawled a cryptic note: “7.3.9 – Database Design.”

She opened , added tbl_Donors , tbl_Pledges , and tbl_Events . She dragged fields into the grid: City , EventName , and PledgeAmount . She clicked the Sigma (∑) Totals button and changed "Group By" to "Sum" under PledgeAmount. 7.3.9 database design in microsoft access

"That," Elara said, sipping cold coffee, "is 7.3.9. Normalized tables. Referential integrity. A query with an inner join. No spreadsheets. No fear."

By midnight, she had five lonely tables: Donors, Events, Volunteers, Inventory, and Pledges. They sat there, disconnected islands of data. She looked at the Excel monster

Elara turned her monitor. The showed a tidy list: Queries, Forms, Reports. She clicked a Report she’d made using the Report Wizard —a professional, printable summary of the drive’s health.

Her boss, Marcus, slammed a coffee-stained printout on her desk. "Fix it. You have one week. Use the company license for... what's that program called?" On the printout, Marcus had scrawled a cryptic note: “7

Elara cracked her knuckles. "Time for a split."