Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
When to Normalize?
Message
From
18/10/1999 07:55:43
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Object Oriented Programming
Title:
When to Normalize?
Miscellaneous
Thread ID:
00277580
Message ID:
00277580
Views:
67
Hi All,
I'm currently working on the invoicing section of a project. Reading JohnK's 2nd tip of the day, got me to thinking about further normalization.

The 2 main tables for my invoicing are currently the parent, Invoice and the child Invoice_items. In the parent I have the normal fields like Cust_ID, Name, Date, Invoice Number, but I also have the payment info ie. Due_30, Due_60..., balance _due, post_date. etc you get the idea. My question is would it be better to further normalize the data and put the payment info in a seperate table. My understanding of normalization is to reduce redundant data, seperating the table in question doesn't appear to do that, it simply puts part of it in another table. What are the advantages of seperating or further normalizing the data, and what are the guide lines for determining when to do so?
Tony
Skill comes from Diligence
Next
Reply
Map
View

Click here to load this message in the networking platform