Sorry to be rude but this a bad design: you should use a single table and
add a field for the date.  This is how relational datas are designed to
work.

If you really want to, you can write a SP that will query for the names of
all of your tables by using either the system tables or the
INFORMATION_SCHEMA views (see m.p.sqlserver.programming or Google for more
details on this), append the names of these tables into query string with
multiples UNION and SELECT and execute this string as your resultset (or
append the data from all relevant tables into a temporary table and select
this last table as the result for the report); however, if you are able to
achieve this, then you should be able to redesign your tables in the first
place.

If you try to keep coding your schema this way - using a different table for
each set of dates - then the number of problems (and headaches) that you
will encounter will keep growing at an exponential rate.