It could also be the workbook with the range is not active. That will
produce an error.

What is different about the environment when you click the button versus
when the userform is active and that line of code is executed?


"MDW" wrote in message
...
I'm in the process of altering someone else's code. He's got a code module
that with code that refers to ranges by name. For instance,

Range("aggregate_loan_monthly_results").Clear

This code was originally called via a macro button on a worksheet. I've
added a User Form that's calling this code instead, and when it gets to
that
line, it errors out with "Subscript out of range". It still works fine if
I
use the button.

What's the deal?
--
Hmm...they have the Internet on COMPUTERS now!