Table Design

[daherb]

I have a table within a database and i was wondering whether or not i should split the table into 2 seperate tables.

The layout of the existing table is to record quotation information ie product codes, cost price, sell price, delivery dates available etc and it also contains fields that allow the user to state if the quote has been authorised or declined, when it was authorised and a number of options to explain the reason the quote wasn't accepted.

QuotationID - Primary Key
EmployeeID - Foreign Key
CustomerID - Foreign Key
EnquiryID - Foreign Key
ProductCode
Quantity
CostPrice
SellPrice
DeliveryDateAvailable
Notes
Authorised - Yes/No field Type
DateAuthorised
Declined - Yes/No field Type
ReasonDeclined
LostPrice - Yes/No field Type
LostStock - Yes/No field Type
LostDelivery - Yes/No field Type
LostCustomerClient - Yes/No field Type
LostNoFeedback - Yes/No field Type

above is the layout of the table, does anyone think that it might be a good idea to split this table into two tables, one table to record the quote information and another to hold the authorisation or decline information??????

 

[ice-9]

I have a table within a database and i was wondering whether or not i should split the table into 2 seperate tables.

The layout of the existing table is to record quotation information ie product codes, cost price, sell price, delivery dates available etc and it also contains fields that allow the user to state if the quote has been authorised or declined, when it was authorised and a number of options to explain the reason the quote wasn't accepted.

QuotationID - Primary Key
EmployeeID - Foreign Key
CustomerID - Foreign Key
EnquiryID - Foreign Key
ProductCode
Quantity
CostPrice
SellPrice
DeliveryDateAvailable
Notes
Authorised - Yes/No field Type
DateAuthorised
Declined - Yes/No field Type
ReasonDeclined
LostPrice - Yes/No field Type
LostStock - Yes/No field Type
LostDelivery - Yes/No field Type
LostCustomerClient - Yes/No field Type
LostNoFeedback - Yes/No field Type

above is the layout of the table, does anyone think that it might be a good idea to split this table into two tables, one table to record the quote information and another to hold the authorisation or decline information??????

you mean, one product table, and one quotetable.
Yes i would slit1

 

[daherb]

you mean, one product table, and one quotetable.

no i mean one table for the quotes and one table for the outcome of the quotes

 

[Big2]

Research Normalization. You can work out what you need in each table using this proceedure, hard to get used to but when u know it, its easy to determine what fields go in which tables. All about redundant data and data dependancies, good luck lol