i make these kinds of tables alot. the reference material out there to step you through everything is pretty lacking and i got through it with alot of trial/error/cussing.
basically you:
1.create a table with as many columns as you think you may need (and if you get the number wrong you can add or remove columns), but you only need two rows (one for heading and the other for the first line).
2. create regions in each cell of the second row.
3. set report parameters per cell.
4. set filters per cell to show or not show particular infromation from the table.
the negative is pro can't count quantities...completely stupid that it can't, but it can't. so to cover that problem in my view i include my quantity number with the part leader/label.
how you handle the drawing numberis by preference or by companystandards. i create a '-x' suffix instance in my table to act as the drawing number and then each instance has a suffix with a real meaning, you could do running numbers as well. i make my drawing with the '-x' instance active so the t-block references it as do the views, but i also will add a view of my generic outside my t-block and then 'erase' the view (the table you create needs to have the generic as it's reference to work...if you come up with a blank table after finishing all the steps to create the table then you know you're not referencing your generic). now, if you don't want to create a '-x' instance version to be your drawing then you will have to use your generic as your drawing and therefore won't have to worry about the extra step of placing a view only to erase it, but i don't like having different parts referencing a specific real part's drawing...could be confusing for whomever's down the road from you. just a couple of ways to skin a cat....
these tables can be saved and imported so if you have similar situations you're not having to redo all the work.
