I've just loaded Excel 2007, and I'm editing/debugging VBA code that was
written with Excel 2003.

My procedures have several calls to other procedures. Everything was
running as it should, until at one point, the code stops calling other
procedures. There was no specific reason for this that I could see. The
code stops cold once a procedure call is reached. In case your wondering, the
procedures in question are all public, and in the same module.

Is there a mechanism (switch?) that shuts off calls to other procedures in
Excel 2007? Perhaps some new security feature that limits procedure
interoperability?

Thanks,

--Alan--

It would help if you could post a (stripped-down?) version of the code
you're using.
Are the other procedures being called in the same module (or workbook) ?

There should be no effect on making calls to other procedures in 2007 vs
2003

Tim

"Alan in Toronto" <Alan in wrote in
message ...
I've just loaded Excel 2007, and I'm editing/debugging VBA code that was
written with Excel 2003.

My procedures have several calls to other procedures. Everything was
running as it should, until at one point, the code stops calling other
procedures. There was no specific reason for this that I could see. The
code stops cold once a procedure call is reached. In case your wondering,
the
procedures in question are all public, and in the same module.

Is there a mechanism (switch?) that shuts off calls to other procedures in
Excel 2007? Perhaps some new security feature that limits procedure
interoperability?

Thanks,

--Alan--

Hi Allan,

I have same problem. The solution of my problem: "Don´t put Show an
Hide methods in the same procedure"

Sds,

Alex Souza

On 20 jul, 17:53, Alan in Toronto <Alan in
wrote:
I've just loaded Excel 2007, and I'm editing/debugging VBA code that was
written with Excel 2003.

My procedures have several calls to other procedures. *Everything was
running as it should, until at one point, the code stops calling other
procedures. *There was no specific reason for this that I could see. *The
code stops cold once a procedure call is reached. In case your wondering, the
procedures in question are all public, and in the same module.

Is there a mechanism (switch?) that shuts off calls to other procedures in
Excel 2007? Perhaps some new security feature that limits procedure
interoperability?

Thanks,

--Alan--