I would take the table with the text date, and either import this into
another table, or just simply add a new column.
What you want here is to make sure that both tables have a true date field
and both are indexed. You can then do a relational join from the first table
to the 2nd table, and get reasonable performance.
Since the table sizes are quite large, then you might keep the files
separate. You could however import both tables from the two different files
into one mdb, and do the join that way. The decision here would depending on
how large the mdb files are.
So, just make a make table query into a new blank database, link to the old
table, and then update this query, and convert the text field into an actual
date field. (just create the table first, and then import). Or, simply make
a new column with the field as a true date type, and run a update query.
update tableDates set newDateField = oldTextDateFieldName
Once you got both columns as a true date type, and index on them, should be
able to get decent performance here..
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada