>No, an explicit cursor isn't necessary. It works fine if you leave the INTO off, other than the query winodw popping up.
>
>Michelle

The situation your describing does create a cursor, (albeit not-explicitly named). I'm just saying that 'into screen noconsole' creates NO CURSOR AT ALL (as far as I can tell).

It will work if do this with only one comboBox on a given form, but if you try 2 at the same time, both comboBoxes (or listBoxes) will contain the same data (I'm assuming you are using rowSourceType=3, and you are thinking of putting 'to screen noconsole' at the end of your rowSource string).