This year, the drive was failing. Queries were wrong, totals didn't match, and Elara had accidentally emailed 400 people promising them "free compost" instead of "free concert tickets."
"Step one," she read aloud, "identify your entities."
By midnight, she had five lonely tables: Donors, Events, Volunteers, Inventory, and Pledges. They sat there, disconnected islands of data. 7.3.9 database design in microsoft access
In 0.3 seconds, perfect numbers appeared. No duplicates. No ghost compost offers.
It was beautiful.
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.
"Now for the magic," she said, opening the . This year, the drive was failing
At 2:00 AM, she built the interface. She used the to create a main form based on tbl_Donors and a subform based on tbl_Donations . Now, when she scrolled through a donor, all their past donations appeared instantly in a tidy datasheet below.
"tbl_Donors (1) <-----> ( ) tbl_Donations"* It was beautiful
She dragged a line from tbl_Donors.DonorID to tbl_Donations.DonorID . A small window popped up:
Marcus blinked. "Is that... a dashboard?"