Frank,

It is generally wrong from a design standpoint to have multiple tables
with similar structure; the correct approach is to have one table with
an extra field to differentiate whatever the different tables do, in
your case Team A from B.

That said, if you can create those tables through a make-table query,
then I suppose you somehow filter table Employee to separate the A's
from the B's, so you are effectively duplicating data in separate
tables. This is not good practice. What you should do is delete the two
team tables, and use two queries instead, just like your make-table
queries, only changed to plain Select ones. This way you avoid
duplication, and your data is readily available at all times, without
the need to "update".

HTH,
Nikos