- #Microsoft visual basic for applications excell hhelp update#
- #Microsoft visual basic for applications excell hhelp windows#
After pressing the f8 key twice, you should stop at the offending VBA statement.Ĭopy-and-paste the offending statement into a reply here, between "code" and "/code" tags embedded between square brackets.Īlso, press ctrl+g to open the Immediate Window. Instead of the runtime error, you should not stop at the Stop statement. But if you already use On Error in the procedure, you might need to be creative.Īdd the following statements just before the procedure End statement: Ideally, that should be the first executable statement. Try the following in order to isolate the problem statement.Īdd the following statement to the offending VBA procedure:
I believe that is a runtime error (right?), and we would need to see the VBA statement and any reference values in order to assist.Īfter you click OK, does VBA highlight the offending statement or part of the statement? Maybe something on my main puter is causing some corruption and that's why I run into it on my other puter, I don't know.
#Microsoft visual basic for applications excell hhelp windows#
Given I'm not running into this with ALL macro-enabled files, and up to this point some I've had the issue with 'correct' themselves, and this is happening on more than one puter (but NOT on an old puter running an older Excel but still Windows 10) it has me frazzled. I don't know if this is the proper place for the question, but I didn't know where else. It's driving me bananas.and I don't even like bananas. Prior to that, I'd even have issues (which still pops up on occasion) where I'd get a 'can't find project or library' error.and macros still in VB wouldn't even show up in the macro list.which I just noticed is true with this current error as well.
Prior to that, I'd sometimes get errors in other spreads when trying to run macros (going into VB would show it stopped on something like a query refresh) The above is what I'm now getting when trying to run a simple macro in one particular file, a file I had no previous issue with and a macro I've run many times for years.
#Microsoft visual basic for applications excell hhelp update#
Lately, I think after an Office 365 update (but I've reinstalled since then and this is happening on my other puter, too) I've had issues.and not always the same ones, and in various spreadsheets (tho I think all are xlsm)