Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Normalization VS Convenience
Message
From
15/06/1998 17:38:28
Jeroen Naus
Harte-Hanks Europe
Hasselt, Belgium
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00108406
Message ID:
00108415
Views:
35
You will find that normalizing your data will be easier for you in the long run. You can solve the issues you specified with either a set relation on two tables or a SQL-select.
Example: If you create a screen with client info (parent)on the top and have the child table in the bottom, you can easily duplicate this screen for all child tables or even better, make the tablename and fields variable and pass them as a parameter so you could use the same screen for all your child tables.
----------------------------------------
CLIENT : NAME
ADRESS
TEL
----------------------------------------
ORDER 1 AMOUNT SHIPPING & HANDLING TOTAL
ORDER 2 AMOUNT SHIPPING & HANDLING TOTAL
ORDER 3 AMOUNT SHIPPING & HANDLING TOTAL
ORDER 4 AMOUNT SHIPPING & HANDLING TOTAL
ORDER 5 AMOUNT SHIPPING & HANDLING TOTAL
----------------------------------------
< OK > < Cancel >

Hoping to be of any help.
Believe me normalisation is the way to go.
Juri
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform