Hi,
Thank you.
I am not quite understand on this:

>>1.Products contains a product ID and a category ID - the first to link to Styles, the second for reporting purposes.

Do you meant 1st is product ID, and second is cateogry ?

>>Styles contains each unique product you sell by color, style, size. I used an integer Primary key, modified to generate a second character field that becomes a barcode. This table also contains a matrix field C(1) that links to the sizing table. As of this moment, the Sizing has 8 records by 18 fields, giving me all the combinations I need for reporting purposes

How is the table structure for this? Can you send me the table strucute 
for this? I think that will be more clearer. Thank you.

When you sell/recieve the item, do you let your client to select the matrix too? How do keep the stock? Does every item with different colour, different style and different size will keep it own qty, or the qty will be increased or decrease base on the product id only? If your client want to know about which colour of the particular product is fast moving, does your program able to show it?

Do you think client want to know about the stock status with very clear (what product with diff colour, diff size and diff style), or they just wan know the product doesn't matter with the colour, size and style?

Thank you very much. Hope canhave a look on your table structure design

:)