Re: why not a one table database ?

Stephane,

As John pointed out, you're on the right track.

Bear in mind that MS Access builds everything, however many tables are being used, in one ".mdb" file. Don't confuse that one "file" as necessarily being the only table. All of the sample MS databases I've seen have used multiple tables that demonstrate the techniques for normalization of tables.

Ron

In article <398f84ee.1919174_at_news.cgocable.ca>, Stephane Gosselin wrote:
> From: taz_at_hy.cgocable.ca (Stephane Gosselin)
> Newsgroups: comp.databases.theory
> Subject: why not a one table database ?
> Date: Tue, 08 Aug 2000 04:08:14 GMT
>
>
> Hi. I need a question answered, if anyone can clue me in....
> a friend of mine just completed a project wich consists of slapping
> together a simple d-b for a local garage. He did it in access, & it
> basically is made up of ONE table, in wich all customer information is
> supplied,(Name,Tel, Address, & a field for the model of the car.
> The customer wants to be able to find his customers just by typing in
> a phone number..... wich in itself is simple. Never having done a d-b
> on a commercial level myself, I tried to ' convince ' my friend that
> he needed two, maybe three tables to prevent redundancy in his data
> For example, if you have 2 customers at same adress..... or 1
> customer with 2 cars ? What defines the number of tables used in a
> small project like this ? Any reading material would be appreciated.
>
> Thanks .
>
>
> Stephane Gosselin
> stef_at_cfusions.com
>
Received on Wed Aug 09 2000 - 00:00:00 CEST