VERY quick summary...
1. Each table should have a primary key. Autonumber is typical, but some tables are better with data entry (ISBN for books, etc). This is a unique value and cannot be (1) duplicated or (2) Re-used if a record is deleted.
2. One table, one topic. For example, if you are taking bookings for a doctor's practice (assuming a single doctor here) you will have
(a) a Patients table with name, address, DOB and other contact details. Each Patient has their PatientID.
(b) a Booking Slots table with Day/Time increments. Each slot has a SlotID
(c) a Bookings table with these fields: BookingID (Primary key), PatientID (Foreign key, Number if PatientID is Autonumber, Text is PatientID is Text). SlotID (Foreign key for Slots, same data type as SlotID in the Booking Slots table).
The 3 table are related thus: PatientID (Patients) to PatientID (Bookings), and SlotID (Slots) to SlotID (Bookings). These are both One to Many relationships (the standard relationship type). Referential integrity should be enforced to prevent you from creating a booking for non-existent patients.
To create a booking, the PatientID and SlotID are entered into a new Bookings record.
Hope this gives the idea ... it's a big topic.
You might find a free download from the Microsoft Knowledge Base useful. Go to the KB, select your version of Access, and type Understanding Relational Design in the search area. Download the zip file -- it's a Word document that goes through the process of setting up the Northwind sample database that shipped with your Office installation.
Denis
