You don't.

Access is a relational database and normalization rules dictate that data be
stored once (and only once).  You are trying to store redundant information
in one or more tables.

Each consultant should be using the "primary table" not copies of that
table.  Now, they can limit the data they see by using queries to only
display the folks they want to see, but they would still be seeing the data
from the main table.

You would need to come up with a way to let the consultant select which
people are shown in their query.  A common way to do this would be to add a
one-to-many relationship where you put a record for each contact and the
consultant number.  In other words, consultant "John" would have a record
with his consultant ID and the ID for one contact.  There would be one
record for each contact "John" needed to see.  Consultant "Sue" would have
one record in that table for each contact she wanted to see, etc.

Then, in your query, you'd include the primary table, and the
"consultant/contact" table.  You would filter the results so that each
consultant would only see his/her contacts.

There are other methods, but that seems to fit well with your scenario.

Hi Imp,

I would question the advisablity of having a separate table for each of
the employees, especially if it is storing the same kind of data.  I
would suggest that you made one table with the all same fields plus an
extra field which you could call employee, link this with your employee
table with a one to many relationship.

Then I think that many of your problems will be solved.

Good luck,

Nick