setting up tables and relationships for a personal book inventory

Lisa Reid 0 Reputation points
2026-07-15T18:51:18.3766667+00:00

Is there someone that I could contact (preferably in person but could try to do online) to assist me in setting up a proposed table layouts and relationships for a massive book inventory that I have acquired and need to better organize. I have used Access but have never before set relationships up and am having some trouble understanding the process. I have created proposed layouts and possible relationship needs for each table in an Excel spreadsheet to better see what I am trying to get my end results to be and make any suggested changes. Any suggestions?

Microsoft 365 and Office | Access | For home | Windows
0 comments No comments

3 answers

Sort by: Newest
  1. Ken Sheridan 3,581 Reputation points
    2026-07-19T14:13:13.29+00:00

    I have used Access but have never before set relationships up and am having some trouble understanding the process.

    For a simple introduction to modelling data in a relational database you might like to take a look at Relationships.zip in my Dropbox public databases folder at: 

    https://www.dropbox.com/scl/fo/0scigd3r48hx5xrev2jrf/AB0-GMdTgMAO5O1cGdr3QW0?rlkey=ib6bs6g9jqcrywwzivur3265t&dl=0 

    This little demo file uses a simple hypothetical medical prescriptions database, and illustrates how relationships are built up across a database to model the underlying reality with related tables, each of which models a real-world entity type. You'll see that some tables model relationships rather than physical entity types. In the database relational model a relationship type is really just special kind of entity type.

    Where a table models a relationship type the relationship is usually many-to-many, between two or more tables. For example the DrugForms table models the many-to-many relationship between Drugs and FormTypes, as a drug might be available in one or more forms, tablet, capsule etc., and each form will apply to many drugs,

    Many relationships will be one-to-many, however, in which case the relationship type is not modelled by a separate table, but simply by means of a foreign key in the referencing table referencing the primary key of the referenced table. An example of this is the relationship between Patients and PatientPrescriptions. Each patient can have many presriptions, but each prescription can apply to only one patient, so the PatientID foreign key in PatientPrescriptions references the PatientID primary key of Patients. Note that a numeric 'surrogate' primary key must be used her rather than the patient's name as personal names can be duplicated, even if combined with other columns. I was once present at a clinic when two patients turned up within minutes of each other, both female, both having exactly the same names, and both having the same date of birth.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. George Hepworth 23,120 Reputation points Volunteer Moderator
    2026-07-15T19:55:50.4933333+00:00

    While I agree with Duane's comments, I do just happen to have two such databases actively in development. Both are online as well as being in Access.

    I can share some ideas, but it's a rather large project. You can explore one of them here: https://gpcdata.com/LTFCatalog

    Was this answer helpful?


  3. Duane Hookom 26,935 Reputation points Volunteer Moderator
    2026-07-15T19:04:55.8833333+00:00

    I applaud you for asking and using Excel to gather specifications. Have you done a search for “book collection ERD database”? I hate sending people to search but it makes more sense than to try provide a concise answer to a somewhat vague question. I suggest searching and then coming back here with specific questions. I would recommend settling on a good naming convention during your planning.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.