my VBA procedures stopped calling other procedures in excel 2007.

A

Alan in Toronto

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--
 
T

Tim Williams

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
 
A

Alex Garcia

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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Outlook to use procedures written in Excel VBA 0
Can this be done with Excel 2007 VBA? 5
Calling Procedures in other Projects 3
I am getting the following error message "Microsoft Office Excel hasstopped working", when I try to 4
Ribbon Button not Working with my Referenced Workbook 2
controling excel from vba access and using sub procedures 3
vba in excel 2007 5
passing values between add-in and worksheet vba code 0

Top