it
sounds like to me that when you do the Save-As, it's trying to
compile, so the debug picks up reference errors, so the "Debug,
Compile" needs to be run first and those errors  debugged and
adjusted as needed before you can use the macro. That would
explain, as Lisa pointed out, why it is firing when you run Save-
As. It's not really processing the callbacks from the combo boxes--
it's trying to compile the entire macro code and it hits those
problem lines and indicates them for your correction.
That would raise the question: is the macro running fine
(without errors) on the original before you try the Save-as?

Or, as other mentioned, it involves an event firing
which needs to be handled.

As far as I know a File Save-As copies the names, too, so those
names should be on the new version, as well. At least, it did that
when I checked using one of mine a few minutes ago.

Or, are you saying you're getting the Run-Time error  after the
Save-As is completed and you're running the program? That doesn't
sound like what you described, but I was just checking to make sure.

Another way to look is: when the Run-Time error appears, and you
hit the "Debug" button, when you hold your mouse curser over
the "rangeText" variable it should tell you what the value is set
at. That might help you figure out what's hitting the error.