Simple Database Required

[Saxman]

I have been asked to build a simple database of customer records. Below
are the fields required.

My problem always seems to be deciding how many tables I will require.
Salutation and Product will require separate tables as I intend them to
be drop-down lists.

What I need to consider is that a customer could have maybe five
different orders.

Do you think the data should all be contained within one table?

Also, what would be best to use as a primary key? Customer or Order
Number? The customer is unlikely to change except maybe their
salutation if they married/remarried. The order number is unique.

The emphasis is on customer records rather than orders.

Order Number
Salutation
First Name
Last Name
Address 1
Address 2
Town
County
Postcode
Telephone
Email Address
Order Date
Order Number
Product
Order Cost
Salesperson
Notes

TIA

[Lyle Fairfield]

Saxman wrote:

I have been asked to build a simple database of customer records. Below
are the fields required.

My problem always seems to be deciding how many tables I will require.

You might benefit by studying the database templates at

http://office.microsoft.com/en-us/te...aspx?av=ZAC000

[Cyberwolf]

You would definitely want to create separate tables here. 1 for the
customer info, 1 for the order info and even 1 for sales person info.
In the customer and salesperson tables create a unique ID using
autonumber. then link these to the order table with a field for each
in it. This will keep your tables nice and organized and if you have
to change customer or sales person info you will only need to change 1
record. I don't see that it is necessary to create a salutation table
just use a drop box on that field. ie Mr. Miss. Ms. Mrs. Dr. etc.

HTH.
Cyberwolf

Saxman wrote:

I have been asked to build a simple database of customer records. Below
are the fields required.

My problem always seems to be deciding how many tables I will require.
Salutation and Product will require separate tables as I intend them to
be drop-down lists.

What I need to consider is that a customer could have maybe five
different orders.

Do you think the data should all be contained within one table?

Also, what would be best to use as a primary key? Customer or Order
Number? The customer is unlikely to change except maybe their
salutation if they married/remarried. The order number is unique.

The emphasis is on customer records rather than orders.

Order Number
Salutation
First Name
Last Name
Address 1
Address 2
Town
County
Postcode
Telephone
Email Address
Order Date
Order Number
Product
Order Cost
Salesperson
Notes

TIA

[chris.nebinger]

Have you looked at the Northwind sample database that ships with MS
Access? Sounds like it would be what you need.

Chris

Saxman wrote:

I have been asked to build a simple database of customer records. Below
are the fields required.

My problem always seems to be deciding how many tables I will require.
Salutation and Product will require separate tables as I intend them to
be drop-down lists.

What I need to consider is that a customer could have maybe five
different orders.

Do you think the data should all be contained within one table?

Also, what would be best to use as a primary key? Customer or Order
Number? The customer is unlikely to change except maybe their
salutation if they married/remarried. The order number is unique.

The emphasis is on customer records rather than orders.

Order Number
Salutation
First Name
Last Name
Address 1
Address 2
Town
County
Postcode
Telephone
Email Address
Order Date
Order Number
Product
Order Cost
Salesperson
Notes

TIA