Inside Relational Databases with Examples in Access

1. Front Matter

   Pages i-xiv

   PDF

2. Introduction

   1. Introduction

      Pages 1-9

3. A simple, single-table database

   1. Front Matter

      Pages 11-11

      PDF

   2. Introduction to Part 1

      Pages 13-16

   3. Tables

      Pages 17-35

   4. Queries/Views

      Pages 36-44

   5. Forms

      Pages 45-53

   6. Reports

      Pages 54-55

   7. Summary of Part 1

      Pages 56-58

4. A multi-table database

   1. Front Matter

      Pages 59-59

      PDF

   2. Introduction to Part 2

      Pages 61-61

   3. Serious problems with single tables

      Pages 62-66

   4. Multiple tables cure serious problems

      Pages 67-72

   5. Making multiple tables work together

      Pages 73-74

   6. Getting the data into the correct tables

      Pages 75-80

   7. Relationships in the real world

      Pages 81-83

   8. How are relationships modeled?

      Pages 84-111

   9. Revisiting the big four — the synergy begins

      Pages 112-126

   10. Integrity

       Pages 127-145

   11. Summary of Part 2

       Pages 146-146

Contents Should we tell you the whole story? Of course, there is an inevitable tension in trying to work like this. For example, in Chapter 16 we talk about referential integrity. There are - sentially six different flavors of referential integrity but Access only s- ports four of them (they are the most important ones however, so you aren’t missing out on too much). The problem is this. Should we tell you about the other two? If we do, as an Access user you have every right to be annoyed that we are telling you about a feature you can’t use. On the other hand, the six different types that we describe are part of the re- tional world and this book is about that world – we are not trying to teach you how to use Access, we are simply using Access to illustrate the relational model. Ultimately we decided to risk your ire and to describe all of the features of the relational model as we see it, even if Access doesn’t support all of them. One advantage of this approach is that if you need to use a different database engine you will almost certainly find the extra information useful. Incidentally, this is not meant to imply that Access is somehow lacking as a relational database engine. The reason we chose it for the first book is that it is such a good example of a relational database tool.

• Access
• SQL
• architecture
• concurrency
• database
• database design
• databases
• optimization
• relational database

• Applied Computing Division, University of Dundee, UK

  Mark Whitehorn

• Seattle, USA

  Bill Marklyn

Mark Whitehorn teaches database design and practice, both to undergraduates and in the commercial world.

Policies and ethics