You can make custom groups (see screenshot)

Julian
Based on your field names, and from looking at a screenshot in a previous post, I think you may want to reconsider your db structure.  Parts are parts are parts.  They should all be in one table:  Parts.  Not broken out into their own table.

Example - lets say you are a chef.  You are going to bake a cake you would have a 1 table for all ingredients.  Not one for Spices, one for Dairy, one for Flour, one for Meat.

Your Recipe is your Assembly.  What parts go into your recipe?

Several videos you should watch:
Chef's Kitchen Helper

Too Many Tables

Normalizing Data

Hi Scott,

I am trying to convert a clipper database over to access. We have spoken to software  guys who told me to use oracle and dot net, but im pc language dull, I have not got a clue.  It is probably why I have created so many tables.

I will upload a few examples of the original database which is opened with DbaseIII

I will now watch Chefs Kitchen Helper, see how I can apply that with mine.

Thanks

Julian -
Sorry I just saw your reply.
Re the software guys - respectfully thell them they are all wet.
I went down that road.  We purchased a Client / Server software that was an Oracle competitor. About 25 years and at that time it was like $15K for the developer license and another $2k per seat for users.
Worst thing is I handed them a working DOS dB IV database - I just wanted it to windows and networkable.
It worked (barely) and half the reason I'm bald today.  LOL

You can find way more people out there to support you by not listening to them AND be able to work on you own db.  Access is scalable if you need the power but for most small to midsize businesses it's great.