Hi,
Happy Eastern to all of you who celebrate by the Gregorian calender.
When I press the macro button placed on the worksheet - nothing happens.
However, if I select the "Sub OpenRacExcel()" and press the play button, it opens the "YYYY-MM-DD RBR V (PR).xlsm", as it is supposed to do!
So far, at least a part of the macro is working.
I have tried to step trough the code with F8, and it marks with yellow the command lines (except DIM commands):
Hovering over it
Hovering over it gives "Application.ScreenUpdating = True"
Hovering over it gives "mainworkBook = Nothing"
Hovering over it gives "PreSelRows = Nothing"
When it comes to the command line:
Hovering over it gives "ActCopyRow = 0"
it skips a lot of code, and the next yellow marked command is at the end:
Nothing happens, no error message is issued. I am officially confused.
Maybe this is the issue:
(I am not allowed to post the link, but there is a blog with the title "Excel VBA Problem With Step Into F8" that says:
"After you record or write a macro in Excel, you can run the macro, or go slowly through it, line by line, to see if it is working correctly. I use the F8 key, ...
However, for the past few months, something was going wrong with the “Step Into” command in Excel 2010, whether I used the menu, or the F8 key.
Code Doesn’t Stop...
In some macros, especially if the code opened another Excel file, when I pressed the F8 key, the code ran to the end of the macro, instead of stopping at the next line of code. That made it very difficult to troubleshoot the code!
It could also cause other inconvenient or embarrassing problems, if the macro was designed to update files, or send out emails. You don’t want that kind of thing happening at the wrong time. "
The solution is offered:
"Finally a Solution Found
Finally, my friend, Ross Connell, found a solution last week, and kindly shared it with me. Ross spent a long time communicating with Microsoft’s tech support, about this and a couple of other issues, and someone there suggested this fix.
The suggestion is not documented on the Microsoft website though, so don’t take this as an official recommendation from them. However, making this change fixed the problem for me, and for Ross. If you’re comfortable in making a change to your Windows Registry, you can try it too, at your own risk."
But I am not sure I want to mess with the registry, especially as I don't know what I am doing with this macro code as well.
Any help?
Thanks in advance,
Nika
Bookmarks