Just a quick note or hint, you want to make sure your field names do not
match key names.  Such as Date is a key name which can conflict within a
query unless you rename your field to Contract_Date or enclose the Date
field within [], [Date].

Classic denormalized design.  What happens if you need to add another
price for a Key/Date pair?

another non-optimal design.  Create ONE table containing all the data
and a flag field that tells you where the data came from (what import
file or whatever).  I'm being picky, right?  Well, consider that you
can create an unbound form that allows you to filter the records any
way you like and then you can base your reports etc on that.

you can use RunSQL to create the tables, but why?  Seems like a lot of
effort for no reason.  What do you do with the data once it has been
processed?

I agree with those who say you should combine the tables with an ID of their
origin to keep them identifiable.  That said you could use code similar to
that below to pick the table to query.

_____________________________________________________
Sub setquery()
   Dim Db As Database
   Dim RS As Recordset
   Dim qry As QueryDef
   Dim strQryFirstpart As String
   Dim strQryWhole As String
   Dim strTable As String
   Dim strQuote As String
   Dim strTableName As String
   Set Db = CurrentDb
   strQryFirstpart = "Select * from "
   strTableName = WhichTable()
   strQryWhole = strQryFirstpart & strTableName
   Set qry = Db.CreateQueryDef("", strQryWhole)
   Set RS = qry.OpenRecordset()
End Sub

Function WhichTable()
   Dim strhandback As String
   strhandback = InputBox("Which table do you want?", "Table to Query?",
"")
   WhichTable = strhandback
End Function
______________________________________________________________

Whether you choose to put all these separate data drops into one large
table or keep them separate my suggestion is to keep a table with one
column that enumerates the tables to be processed. You could use this
meta-table as it were as the record source for a combo box to streamline
your analytics, or macro/VBA code that handles appending all the
sub-tables into the master table. In either case you could look to the
meta-table for table names and build specific SQL statements (in code)
from that.

HTH