|
-
Nov 3rd, 2004, 07:41 PM
#12
Hyperactive Member
In addition to vince's design, you could have ProductID and ProductNumber. Use the ID because it's faster to index on a numeric field. Use the Number to get the user's preferred product code. You could then apply this to all your table, always referencing the ID.
Regarding the supplier and product, keep in mind that a product could have multiple suppler and, of course, a supplier always has multiple products.
Also, why do you need to have separate table for Product, or I think you shold rename ProductDetails for I think it's purpose is not in it's name.
Additionally, I think it's better if you make all your primary key a Required field.
Last edited by dRAMmer; Nov 3rd, 2004 at 07:45 PM.
live, code and die...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|