On the database design ...
It is very rare for a database design to 'become relational in the future' -
more often, if you start with a flawed design, you're stuck with it forever.
It's kinda like laying the foundation for a house - if you don't get it
right before you build the walls and roof on top of it, you're not going to
get it right afterward.
The ten-table design is, in the long term, unworkable. If your supervisor
can't see that, well, we can sympathise, but there's nothing we can do about
that. That's a people problem, and we can only help with technical problems
here.
On easy solutions ...
'Easy' is, of course, a relative term. I think writing a UNION query is
pretty easy. While you can't use the graphical query designer to create a
UNION query, what you can do is to use the graphical query designer to
create a query that selects from one table, then switch to SQL view, copy
and paste the SQL created by the designer, then you just have to modify it
slightly for each of your UNION clauses. For example ...
SELECT Table1.TestID, Table1.TestOne, Table1.TestTwo
FROM Table1
UNION SELECT Table2.TestID, Table2.TestOne, Table2.TestTwo
FROM Table2;
The first two lines above ("SELECT ... FROM Table1") were created by the
graphical query designer. I then switched to SQL view, copied the first two
lines, and pasted them back between the end of the original two lines and
the closing semi-colon. I typed in the word 'UNION', and I changed each
reference to 'Table1' in the second two lines to 'Table2'.