Others

How to Design an Access Database for Multiple Lease Contacts and Parcels

Chanuka GeekiyanageChanuka Geekiyanage Nov 3, 2026 869 views

Question details

The user needs to structure a database schema to efficiently manage leases, multiple parties, and multiple parcels without duplicating data.

How to Design an Access Database for Multiple Lease Contacts and Parcels
Product
Microsoft Access
Device & OS
not provided
Scenario
Designing a relational database for property management or real estate to handle many-to-many data relationships.
Observed behavior
Storing all contacts and parcels in a single lease record causes maintenance difficulties and leads to data duplication.
Before you start

Before structuring your tables, clearly map out your business rules to determine if the relationship between parcels and parties is strictly one-to-many or a complex many-to-many.

Solution 1Recommended

Set Up Base Tables and Junction Tables

Create separate tables to handle the many-to-many relationship between leases and parties.

A lease can have multiple parties, and a party can be involved in multiple leases. This many-to-many relationship requires three separate tables to function correctly without data duplication.

1
Create the base tables

Create a 'Parties' table for people or entities and a 'Leases' table for the lease contracts. Assign a Primary Key (e.g., PartyID and LeaseID) to each.

2
Create a junction table

Create a third table named 'Party_Lease'. This table will act as a bridge between the Parties and Leases tables.

3
Add foreign keys

In the 'Party_Lease' table, add PartyID and LeaseID as foreign keys. Together, they will uniquely identify each party associated with each lease.

4
Set a composite primary key

Select both foreign key fields in the junction table's Design View, then click the Primary Key button to create a composite primary key.

Set Up Base Tables and Junction Tables
Handling Parcels: If every party is associated with every parcel, add a 'Parcels' table referencing the 'Leases' table. If parties link to specific parcels only, use another junction table like 'ParcelParties'.
Free Microsoft Office alternative

Looking for a Free Office Suite? Try WPS Office

While Microsoft Access handles complex relational databases, for everyday documentation, spreadsheets, and presentations, WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office. Seamlessly edit Word, Excel, and PowerPoint files without a subscription.

Free and lightweight alternative to Microsoft OfficeFully compatible with Microsoft Excel (.xlsx) formats for simplified data trackingFamiliar, tabbed user interface for easy migration from other office suitesBuilt-in PDF editing, conversion, and collaboration tools
microsoft office alternative - wps office

Frequently Asked Questions

What is a junction table in Microsoft Access?

A junction table is a database table that contains common fields from two or more other tables within the same database. It is used to resolve many-to-many relationships, such as when one lease has multiple parties and one party has multiple leases.

Why shouldn't I put multiple contacts in the same lease record?

Storing multiple contacts in one lease record violates database normalization rules. It makes the database harder to query, requires changing the table structure if the number of contacts exceeds your predefined fields, and leads to redundant data entry.

How do I create a composite primary key in Access?

In the Table Design view, hold down the CTRL key and click the row selectors for the fields you want to include (e.g., PartyID and LeaseID). Then, click the 'Primary Key' button on the Table Design ribbon.

Can I manage lease data in a spreadsheet instead of a relational database?

Yes, for simpler data models, you can use spreadsheet software like WPS Spreadsheets or Microsoft Excel to track leases using flat tables or PivotTables. However, for complex many-to-many relationships, a relational database is more robust and prevents data duplication.