Search results

  1. A

    Create proper relations

    Will do....May be if I post the relations initial take, I can get better guidance. I will be back !!! Thank you for sharing the link
  2. A

    Create proper relations

    I have the following tables: 1. Client Table 2. Client Farms ( each client has one or more farm) 3. Client Crops (what the client produces, and the seasons they use) The products we sell have these tables 1. Products 2. Stresses the products cure ( Product can cure more than one...
  3. A

    A very large table and a solution

    I see, So Phone "group" table will be PhonetID PK Phone PhoneType ContactID FK And if any group has the same characteristics, the many will happen again Family members for example tblFamily FamilyID PK memberName memberRelation (1 Spouse etc) ContactID FK I will have a...
  4. A

    A very large table and a solution

    I did not doubt your design at all, and just to comfort you. m$ did it BIG SCALE when allowed in Access the multi value field. They blew Rule #1 to pieces. And all that for the sake of marketing. Please explain to me how ONE Entity (The Contact ) become One To Many by splitting the Entity...
  5. A

    A very large table and a solution

    Cronk, I am trying "hard" to follow your logic...so, TableCD will have one record for each cd and FK for the owner TableOwner is again one record per owner. They can own several CD's There is one to many relation bet TableCD and TableOwner. How this relates to my issue of splitting I do...
  6. A

    A very large table and a solution

    Cronk, That what "the gurus" objected to......denormalizing. The Phone data belongs to a primary key in the client so why put it in a separate table with ANOTHER PK......At least that what I understood from Rule #1 in Normalization.
  7. A

    A very large table and a solution

    I got two "why"s .....That is good start ...I am on the wrong lane.!!!! Outlook has 92 fields but nicely grouped ( Home, business etc) So, I design ONE table and I pass rule number one in normalization and keep you both happy ;) How do I maintain such a huge table ?? I will...
  8. A

    A very large table and a solution

    I have a Contact Table that has data as huge as a contact in outlook ( many many fields). I decided to split it into groups and hence separate tables The Main table has the absolute minimum and also functional ClientID (PK) auto company name First/last name Mobile Then followed by...
  9. A

    Two appraoches in table design

    Pat, you came to my rescue....again...
  10. A

    Two appraoches in table design

    A product can be used by many Clients, As A client can use many products. So, you selected Approach I. In this case I have to create a composite primary key ( Client PK + Product PK) to avoid duplicates. Right ?? I am still hoping that some one "shoots" Approach II and tell me why...
  11. A

    Two appraoches in table design

    Tables client and product. It is many to many 1. Approach I Unique Client table and Unique Product table and Junction Client/Product table 2. Approach II Client with product FK, and Product with Client FK and the junction table. The nature of the project is; Clients will grow, but products...
  12. A

    There must be a better way to validate data entry

    With people like you, I wake up looking forward for another beautiful day.....
  13. A

    There must be a better way to validate data entry

    I agree , my idea is very crude, but may be if I use VBA I can clean it up, after all , what I need is to create the elements of an array to feed the combo box. As for the One Table solution given above, I made a first attempt and it worked. Thanks. Using KISS!!, I created the tblLookup with 3...
  14. A

    There must be a better way to validate data entry

    Pat, It is obviously a well thought approach and I will spend some time studying it , then adapt it for my needs. For a quick fix, let me indulge you a bit in the following idea. If I create a tblReferance, each column represent it's own data validation list. ( This table will replace the...
  15. A

    There must be a better way to validate data entry

    Thank you Pat for your support. Yes, that what I wanted to say...Lookup in Tables where I put a list of text fields INSIDE the table design. I will look at your work and I might come back with questions. Thanks again.
  16. A

    There must be a better way to validate data entry

    I am auditing someone else Database. It consists of 4 entities and some associative tables. A MAJOR part of the tables (15 tables) are nothing but lookup tables to insure valid data entry. I call them reference tables. They are mostly STATIC.( City.... ). Whenever you design a form for data...
  17. A

    How safe using combobox to input foreign key

    In a Related Tables, you need to enter a FK to link to the other table. You either key in the FG from memory !!!!!! or use help. The standard procedure is to design the field as combo box AND use SQL to select the field that will help to input the ID of the other table. So, if you want to input...
Back
Top Bottom