Can someone please evaluate my Normalization. Please
As others have requested, the only possible way to offer useful feedback is to start with a solid description of the business purpose for the relational database application, along with a complete, comprehensive statement of all of the business rules governing it.
It appears that you have some sort of selling operation. "Items" appear to be the names of products offered for sale. So start there. What is the reason for creating the application and what rules do you have to follow for it?
Normalization doesn't occur in a vacuum. It can't be abstracted out of the context. To give one simple example. You have a table of "Items" and a table of "Brands" and a table of Branded Items. The design there must reflect a business rule--we have to assume--that each of the items in the inventory can be sold by one or more vendors under different brand names. Another possible business rule, of course, would be that products are all from one supplier and of one brand. The type of business you run determines what the rule should be and that in turn determines whether the table design is appropriate.
But that's only an assumption based on what is here. You need to validate that assumption as one part of the explanation for the business purpose and business rules that apply.
By the way, you have used the insufferably annoying Lookup fields in your tables. They are a crutch for newbies, but unfortunate in a good relational database application. Lose them, please, and use only standard Foreign Key fields. Along the same lines, there's some tricky naming going on with many of those fields. I'd recommend a close reading of some good references on naming conventions. Many of these tables have the same two fields: "ID" and "NameVal". That's a recipe for confusion, especially when combined with the pernicious Lookup fields.
That said, of course, naming is a personal choice, and if you don't get lost in it, fine. I would not want to have to work with this naming convention, though.
And finally, one of the things I've learned over the past three decades is that the pursuit of a "perfect" anything is futile. Forget "perfect". Implement the most effective data model for your specific business.
