I should mention first that table lookup fields are considered poor practice - unless maybe you're one of a very few that would be using the db, and the data in those fields is rarely changed, and the lookup is for doing things like selecting from a limited controlled list (again, once in a blue moon and by few people). If you can't say that, save yourself some grief and redesign.
If you insist or just want to learn how to drill down to the value of a lookup field, your query criteria needs to make use of the .value property of these types of field, such as WHERE Empl.Value = forms!myFormName.myControlName where Empl is the name of the field in your query design view. The problem is, what you see in the table is not really there - it is the result of hidden pointers to the source. What's really in the table is the value of the pointer. You are only going to have more trouble with this if what you're doing doesn't meet the test I outlined.
P.S. a more descriptive title for your post helps people decide on whether or not to pursue it, and helps in future searches.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.