Normalizing a Database

[tehbrosta]

I am taking an online class and I decided to break the mold and not use one of the supplied databases as my project. The professor told me that if you want to do this make sure the database is normalized. I understand this concept but would like some experts to take a look at it. I have to have this down before I proceed on the rest of the project since everything builds off this.

A client can have many HOSTINGSUBCRIPTIONS


Each HOSTINGSUBSCRIPTION can only be linked to one HOSTINGPACKAGE
A client can have many INVOICEs
INVOICEs can have many LINEs

I believe HOSTINGSUBSCRIPTIONS and HOSTINGPACKAGE is correct, but INVOICE and LINES are not. It should be a M:N relationship, but I'm not sure how to properly show that.

[RuralGuy]

It is fine if all of your PK's are AutoNumbers. You also do *not* need to involve the FK in the PK of the Line table.

[tehbrosta]

It is fine if all of your PK's are AutoNumbers. You also do *not* need to involve the FK in the PK of the Line table.

I'm not doubting you, obviously you know what you are talking about but the reason why I did that is so I could have a unique key. LINE_NUM is the order of how items show up on the INVOICE.

[RuralGuy]

So you want the LineItems to be in a paticular order and you set that when you add the line item, right. If you do not care about the order but like line numbers then those could be assigned dynamically at run time. Otherwise what you have is just fine not that you explained the LineNumber field.

[tehbrosta]

So you want the LineItems to be in a paticular order and you set that when you add the line item, right. If you do not care about the order but like line numbers then those could be assigned dynamically at run time. Otherwise what you have is just fine not that you explained the LineNumber field.

I am explaining each attribute now. Thanks for your time.