It sounds like to want to add a Table called 'Assembly'. One record in it is a unique assembly (or up to 35 parts, in your terminology).
You then want a Join Table, call it AssemblyParts. You need a Join table as I assume you can use the same part in many assemblies, so your relationship from Assembly to Parts is many-to-many.
The Join Table has one record for each part in an assembly. You could have Assemblies:
001 Large Assembly
002 Medium Assembly
003 Small Assembly
If Large Assembly has a nut and a bolt, and Medium Assembly has a nut and a screw, and small assembly has a nut, bolt, screw, and strut, the Join Table will have 8 records in 3 fields, AssemblyID and PartID and QtyRequired:
AssemblyID PartID QtyRequired
001 002 4
001 004 2
002 002 1
002 001 6
003 001 7
003 002 1
003 003 1
003 004 3
The relationships are:
Assembly Table Join Table Parts Table
Assembly ID --------> AssemblyID PartID --------------> Part ID
Then in the Assembly Table show a portal drawn from the Join Table, and it will show all the components and their quantities in that assembly. If you want you can in the Parts Table draw a portal to the Join Table and it will show all the assemblies that use that part and what quantity each requires.
You don't need, or want repeating fields. And there is no '35' limit to this; you can have as many components as you like.
Search the forum for 'Join Table' and you'll find lots of useful examples.
It worked great. My databases work great now. Many thanks. Cordially, Dave Wilson