Offhand, I'd say you have a bad database design.
What purpose is there in having each game in a separate table? Are the other fields in each of the separate tables SIGNIFICANTLY different from one game to the next? If not, they should be all in one table, which would simplify not only this task but many future task a lot.
Even if there are some fields that need to exist specifically for a given game, you'd be better off pulling all the common fields together into a single table and then only do the separate tables for the significantly different fields.
Read up on "normalization."
An optimist sees the glass as half full.
A pessimist sees the glass as half empty.
A realist drinks it no matter how much there is.