I don't know exactly why it doesn't work, but it's *WAY* overly complex.
I *REALLY* have to ask WHY you would store the id and value in a cookie and then go to that other AEmployees page instead of just passing the id and value as part of a form posting?
That implies that when you get to AEmployees.asp you have to use Request.Cookie() to get those values, right?
What about simply:
SqlStr = "Select DISTINCT Unit From Employee Where PhoneBook = 1 Order by Unit;"
Set UniNme = Connection.Execute(SqlStr)
Response.Write "<select id='Unit'> "
Response.Write "<option value=''>Choose Unit</option><br>"
Response.Write "<option value='Everyone'>Everyone</option><br>"
Do While Not UniNme.EOF
Response.Write "<option value='"&UniNme("Unit")&"'>"&UniNme("Unit")&"</option><br>"
Response.Write "Name Search: <input type='text' id='MySrch' >"
document.getElementById("Unit").onchange = Change;
document.getElementById("MySrch").onchange = Change;
if ( this.value == "" ) return; // nothing searched for?
document.cookie = "Temp1="+escape(this.id);
document.cookie = "Temp2="+escape(this.value);
Yes, the JS code must go *AFTER* the end of the ASP code.