Quote Originally Posted by magneteye View Post
Six fields.

Sizes of clothing.
This would be a classic reason for using attributes.

Quote Originally Posted by magneteye View Post
I created a table called products_sizes and added 6 fields, one for each size (small, medium, large, xlarge, petite, plus sizes).
If I correctly read your proposed structure for the products_sizes table as being a reference table, your needs are more directly reflective of pulling data from the Manufacturers table and simply storing the selected choice into your new "product_size" field in your products table:
- query the table
- build an array of its entries
- display a pulldown
- store the selected entry
- then in the storefront, display information appropriately based on the selected setting
- and build your shop-by-size choices in the category menu

Quote Originally Posted by magneteye View Post
Lastly, I want to add the sizes to the end of my categories menu so a user can shop by size.
That's yet another kettle of fish ... and doing it by using normal attributes would be admittedly more difficult. Using a dedicated size table as you're considering may be a touch easier. Nevertheless, I recall a contribution floating around some time back that had code for shop-by-size in it. It should be in the downloads section if you want to use it as a reference. I think it was attribute-based.