Quote:>> There is a lot of fields [sic] in the feeOrderTbl that aren't in the
feeTbl, like delivery notes, warehouse location.... <<
You might want to drop those silly "-tbl" postfixes and start using
proper data element names as per ISO-11179; this is SQL and not BASIC.
Columns are not fields, rows are not records and tables are not files --
If a fee order is a sub-species of Fees, then you should consider a
table that contains the extra attributes and relate it to the Fees table
with DRI actions. This is one of the many reasons a table is not a file
and a column is not a field. You do not design one table at a time,
like you did with files. You design an entire schema at once, as a
complete model. And the goal is to remove redundancy in the data
(normalization is only one tool for doing this).
You are storing the same data in two places, thus subverting the reason
we moved from file systems DBMS.
Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, datatypes, etc. in your
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!