Question Help with normalising database as attached

[PhoenixCouriers]

hi all,

was wondering if anybody can help with this and check that the database looks ok

I have now adjusted the database slightly and was wondering if you could have a look and see if this is Ok.

You will notice that the customers details are all contained in 1 table and this is fine the way are customers table works so do not need to have adjusted as this is how the old one was created and has been fine for over five years so would just like to leave that as it is.

The main areas I need to look at is the invoice and invoice details tables.


many thanks


simon

 

[MarkK]

I would have an address table. CollectionPoints, Customer Billing and Shipping addresses, and DeliveryPoint all support their own address. I would abstact that.
CollectionPoint and DeliveryPoint have exactly the same strucuture so I would handle them in the same table. Have a yes/no field for IsCollection and/or IsDelivery.
It seems odd to me to ask for feedback and then say what feedback you'll reject. Your call obviously.
Cheers,

 

[PhoenixCouriers]

hi there, thanks for reply
the reason we have it like that is that there will always be 4 address's involved

INVOICE ADDRESS
WAREHOUSE ADDRESS
COLLECTION ADDRESS
DELIVERY ADDRESS

as me might collect from their supplier and deliver to one of their customers so will always have seperate collection and deliry point?