I think everyone is trying to tactfully hint you need to study some. Believe me, I get lots of pompous responses from people (not on this forum of course) when I ask a simple question, but the point being made is that you're asking for help on something that requires understanding of relationships.
There may be 10 games per physical sheet, but that's not how it works in relational databases - USUALLY. The reason is that each game has (from your table) 3 parameters, and each game is really equal in many senses, and you want to be able to search all games. so instead of creating a table with these fields:
Table: Sheets
game1
param1A
param1B
game2
param2A
param2B
game3
param3A
param3B
.. etc .. etc ..
[..please say you understand that :-]
you create TWO tables:
Table: Sheets
ID INT(9) auto_increment primary key
Name CHAR(30)
Table: Sheets_Games
ID INT(9) auto_increment primary key
Sheets_ID INT(9)
Idx TINYINT(2) unsigned
Description CHAR(30)
ParamA CHAR(30)
ParamB CHAR(30)
Each sheet has an autoinc ID assigned.
Then each game goes in Sheets_Games, and Sheets_Games.ID is a new number for THAT game. Sheets_ID refrences Sheets.ID. Idx is the game sequence number.
You see now all games are equal? They can be searched on 3 columns, Description, ParamA, and ParamB. (vs. 3x10=30) They just have a Sheets_ID pointing back to the sheet and that structure can be rebuilt by a joining query if need be. Not only that, you can have 10 games per sheet, OR only 3, OR 3,000,000,000 if you want - so you save space.
I've just given a lesson in normalization - which you could have learned by study. Hope that helps, this is what ramjet was getting at I think. Point is, there are more things to learn in this new way of thinking, and if you're going to run with the big dogs you need to learn how to eat meat :-)
HTH,
Samuel