How to Create a Microsoft Access Database for Herbs and Health Issues
Question details
The user wants to design a relational Microsoft Access database that links herbs to health issues without duplicating data, supports many-to-many associations, and includes reference information.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Planning a database structure for herbal reference information and health issues.
- Observed behavior
- The user needs a design that avoids duplication, allows one herb to relate to multiple issues and one issue to relate to multiple herbs, and supports searches by issue.
Before designing the tables, list the main fields for an herb, such as name, botanical name, and parts used, and the main fields for a health issue, such as issue name and symptoms. Decide which reference details belong in separate tables so the main tables stay normalized.
Design a Normalized Access Database with a Junction Table
Use this solution when creating the database from scratch and you need a maintainable many-to-many relationship between herbs and health issues.
A junction table stores pairs of primary keys from two related tables. This prevents repeating herb names or issue names and allows flexible many-to-many searching.
Open Microsoft Access, click Blank database, and create a table named Herbs with a primary key field HerbID set to AutoNumber and fields such as HerbName and BotanicalName.
Create a table named Issues with IssueID as the primary key and fields such as IssueName, Symptoms, and Notes.
Create a table named HerbIssues with fields HerbID and IssueID. Set both fields to Number or Long Integer and make the combination of HerbID and IssueID the primary key.
Open Database Tools, click Relationships, add Herbs, Issues, and HerbIssues, then drag HerbID from Herbs to HerbIssues.HerbID and IssueID from Issues to HerbIssues.IssueID. Enforce referential integrity for both relationships.
Click Create, open Query Design, add the Herbs, Issues, and HerbIssues tables, include HerbName, IssueName, and other fields, then filter by issue to display all associated herbs.

Start from an Access Inventory or Asset Tracking Template
Use this solution if you prefer to learn from an existing Access template and then adapt it to herbs and health issues.
Use WPS Office as a Free Microsoft Access Alternative for Herbal Health Records
WPS Office does not include an Access database application, but it gives you a free, lightweight way to create herb and health issue reference documents and spreadsheets that remain compatible with Microsoft Office formats.
- 1. Download WPS Office: Go to the official WPS Office download page and install the free version for Windows, macOS, Linux, or mobile.
- 2. Open WPS Spreadsheets: Launch WPS Office, click Spreadsheets, and create a new workbook for herbs, health issues, and reference notes.
- 3. Save in Microsoft Office format: Use Menu, click Save As, and choose .xlsx or .xls to keep your workbook compatible with Microsoft Excel and other Office applications.

Frequently Asked Questions
Does WPS Office include an Access-like database application?
No, WPS Office includes Writer, Spreadsheets, Presentation, and PDF tools, but not a relational database engine like Microsoft Access. You can use WPS Spreadsheets to maintain herb and health issue lists, but many-to-many relationships are easier to model in Access.
What is the purpose of a junction table in Access?
A junction table stores pairs of primary keys from two tables, such as HerbID and IssueID, so one herb can link to many health issues and one issue can link to many herbs without duplicating data.
Can I use an existing Access template for herbs and health issues?
There is no built-in herbs template, but inventory or asset tracking templates can provide a useful starting structure. Open File, click New, search for inventory or asset tracking, and then adapt the tables and forms.
How do I search for all herbs associated with a health issue?
Create a query that joins the Herbs, Issues, and HerbIssues tables, then add a filter on IssueName or IssueID. Run the query to see the matching herb records.
How should I handle sources or research notes?
Add separate tables, such as Sources and Notes, and link them to Herbs or Issues with one-to-many relationships. This keeps reference information separate and makes the database easier to maintain.




