Before we get too deep, I want to emphasize that this is your project. If you want to split, fine. If you want to know how to keep it together, fine.
THEORY says you should not split a table that contains things that have the same function in your business. You should merely qualify the items with a class-code that says, this is a camera, that is a projector, this is a left-handed veeblefetzer.
But for folks not used to Access, that is a confusing statement because you often don't realize exactly what you are doing at a higher viewpoint. So excuse me if I put on my "professor" hat for just a moment.
Access is a business modeling tool, one of many such products. It is just not as clear that that it is such a tool. But ALL database tools of any quality allow you to make a "model" of your business. Let's say that your business is a retail store. OK, what do you do in a retail store? You SELL things. So what is your business model?
Well, you have inventory in stock from suppliers. You can have orders pending. You sell inventory from stock (or from back-order lists) to customers. What does that mean in simple terms regarding business models and Access?
It means you would have tables for your suppliers, customers, supply orders, and product line information. These tables would have relationships based on matching keys. Read up on "database normalization" before you go too far with this, but let me get to the point of why you don't split your product line table.
In your business model, your cameras, speakers, and other items all play they same role. They are items to be bought, stocked, and sold. It doesn't matter whether they are cameras, speakers, left-handed veeblefetzers, or Christmas ornaments.
If you want to keep separated product descriptions for special purposes, there are ways to do this that keep the base product descriptions together and just have separate detail tables for the things that cannot be retained in the base table because sometimes the descriptives just don't fit. But you must not lose sight of the purpose of your inventory. Splitting the tables into product types might lead to that point.
