- Local time
- Today, 07:23
- Joined
- Feb 19, 2002
- Messages
- 43,408
That isn't the way relational databases work.I have to have some fields the same becouse this way user will know what item he is using.
We talk a lot about "normalization" which is the process of defining entities and attributes and ensuring that attributes will not be duplicated in related tables because that leads to potential inconsistencies. i.e. different values for the same attribute in different tables. For example. You would have CustomerName as an attribute in tblCustomer but it would never occur in tblOrder because tblOrder would include a foreign key (CustomerID) which points back to CustomerID which is the PK in tblCustomer. What we don't talk about specifically is how to turn all those normalized tables back into useful data. That we do by using queries. So, if you have a form where you want to show the CustomerName for an Order, you would use as the RecordSource for that form, a query that joins tblOrder to tblCustomer so you can pick up related values. For safety, you would NEVER allow columns from tblCustomer to be updated on a form which is intended to enter an Order. Therefore, on the Order form, ALL controls bound to columns selected from tblCustomer would be locked to prevent changes.