The table you are trying to generate correctly represents a many to many relationship type between labs and methods, whereas your original table is an example of what is known as
'encoding data as column headings', which violates one of the fundamental rules of the database relational model, the Information Rule (Codd's Rule #1) which requires that all data be stored as values at column positions in rows in table.
The restructuring of an incorrectly designed table like this can be automated, and you'll find an example as UnencodeColumns.zip in my public databases folder at:
https://onedrive.live.com/?cid=44CC60D7FEA42912&id=44CC60D7FEA42912!169
Note that if you are using an earlier version of Access you might find that the colour of some form objects such as buttons shows incorrectly and you will need to amend the form design accordingly.
If you have difficulty opening the link copy its text (NB, not the link location) and paste it into your browser's address bar.
In this little demo file, although your source table has Boolean (Yes/No) columns the example for Quantity in Stock values would in fact be the appropriate one in your case as you wish to store the Boolean values in the third column, Selected, in your final
table rather than having a two-column table in which each row repesents a selection. The StoreStock_Vals table in my demo is analogous to the table you wish to generate. In your case, rather than quantities the values would be Boolean TRUE or FALSE values