I figured out what is happening, Naomi...

It is the KEYBOARD '{ALT+DNARROW}' - if that is in the GotFocus event, and you SetFocus to the box programmatically, it works fine, but if you click on the little arrow on the box, then it seems to 'double fire' - it will drop down, and then close again, so if you add an IF to the GotFocus to check if the memvar is empty, or not, it will do the Keyboard action if the memvar is empty, so, if you are returning for another choice, the memvar isn't empty, and the list doesn't drop down automatically - it requires your mouse click, and thus is doesn't fire twice.

It has nothing to do with the data source for the box, which I DO agree needs work, but they asked for the box to work properly, and I have made that happen. If they want more work to bring the other stuff in line with better programming conventions, then so be it, but I have corrected what they asked for.