>In response to the second part - - maybe the first part too! The SQL statement populates the dropdown combo fine. During the same session, the following happens.
>1. User updates a record via the form and uses the dropdown combo to select a name (Smith, John). User saves this record. The first time in a new session, the combo dropdown is at the beginning of the name list (alphabetical by last name)
>
>2. User moves to the next (or any other record), when the user uses the same dropdown box, the SQL record pointer is pointing at the SAME (Smith, John) name as was used to update the previous record. The normal method of selecting Smith, John doesn't work. User has to move to another name - then move back up to Smith, John before they can select Smith.
>
>This isn't a critical point - but irritating. Surely there's a way to tell the SQL to GO TOP or something - - I just haven't found the right place to put it.
>Thanks for your earlier response.
>
>Linda

You are right, there should be GO TOP somewhere to ensure that the record pointer will move to proper record. The place for it doesn't mean much.