I have definitely seen the situation where I have Option Explicit, as I
always do, and a non-declared variable is not picked up on compile. When
executing the code, it only gets picked up when that path is traversed. I
have never been able to spot a common situation, but it is far more regular
than I would like.



Bob

"Barb Reinhardt" wrote in message
...
I just received a report from a user testing a workbook in work, that a
variable is not defined in the procedure. What's strange is that the
variable is defined. Has anyone else seen this problem and what is the
solution.

FWIW, I have option explicit on every module and when I compile the code,
there are times when errors like this aren't captured. Has anyone seen
that
as well?

Thanks,
Barb Reinhardt