Relationship Graph design: Advice needed

[Treigh]

Hi there,

I've just designed a solution made of 9 essential tables to help a friend manage his customers. My friend owns a moving company and wants to be able to track his daily transactions in a database.

Here are the main tables:

-------------------------

[color:red]VIEW PDF ATTACHMENT FOR BETTER INSIGHT

CUSTOMERS, JOBS (ORDER), ORDERLINE, SERVICES, INVOICES, PAYMENTS, PRODUCTS, EXPENSES, REFUNDS

One customer can book many jobs (orders), but a job can only be assigned to one customer at a time.

An invoice can receive many payments, but a payment can only be applied to one invoice at a time.

My questions:

----------------

1) is my Relationship graph OK?

2) How should I relate the refunds table to the rest of the graph?

How should I best design my graph if necessary.

Thanks in advance

EC_ERD_Sample.pdf

Edited September 9, 2009 by Guest