I didn't fire up Excel to test what the error message would be, but as a
habit I always use Option Explicit and avoid using variants whenever
possible.

I didn't think of the possibility of changing the combo name... Having
programmed in VB for some time I have gotten in the habit of using a
meaningful name for all UI controls and a prefix for the type of control...

Also, clicking on the debug button when the error comes up (since it is a
runtime vs compile error) should point to the exact spot in the code where
the error is/was...

David

however, if the OP's not using option explicit, vba will treat it as a
variant and the code will still run. If he was using option explicit,
he'd
get a compile error stating "variable not defined", not a run-time error.

I would ask the OP to double check the name of the combobox. Is it
actually
named combobox1 or did he change it and forget to change the code? His
code
runs fine on my machine (I have to remove SearchFormat:=False as I have XL
2000). Also, I would qualify Combox1 w/the name of the form, but VBA
didn't
seem to mind.