Heeeeellllllllpp!

I'm sure my macros didn't used to do this but now when I run a macro that I use regularly, Excel opens up the code window as well. This was helpful while I was writing and debugging the code but now that everything runs as I'd like it has become rather irritating. My macro would also be useful for a few other people in the office whom I'm sure would just want to be able to run the macro whilst having no interest whatsoever in reading my shonky VBA every time they run it.

Google is failing me on this. Have I missed an obvious tick box somewhere?

Is it anything like this?

Unfortunately not, that thread title had me all excited but alas it doesn't matter whether my code window is maximised or not when I run the macro. I get the code window opening either way.

Which version of Excel? You don't have any personal macros set up to run do you? Have you tried hiding the offending Modules? Security settings?

I wonder if you can delete any default/profile settings and get Excel to recreate them?

You haven't just upgraded Excel or Windows have you? Or installed any updates?

It affects both Excel 2010 and 2013 on both my home machine (just upgraded from Windows 7 to 10 but the issue has existed both before and after the upgrade) and my work one (Windows 7). I can check Excel 2016 later.

What do you mean by personal macros? I wrote the code if that's what you mean. There is one module containing two macros.

Not sure how to hide the module, if I right click in the code window and hide it, all it seems to achieve is to hide the project explorer.

Security settings are the default, no password protection. Putting a password on viewing the code just succeeds in making it read only but still opens the window.

On the plus side I've just learnt how to use Windows 10's new screen video capture utility although it doesn't show anything useful in this case as it only shows the main Excel window but not the code one opening.

Haven't tried playing with any profile settings on this machine as I'm using it to work from home for the next 3 days so am a tad reticent to do that.

Same issue on Windows 10/Excel 2016.

AndrewR will have a fit if this gets sorted before he has had a chance to reply

The lair of the white worm is a great film. Has anyone else seen it?

Might be a silly question but how are you launching the macros?
Have you the developer menu options visible, if so try disabling them.
Also, have you had another monitor or projector attached, if so make sure you are set for just one display...

There's no such thing as a silly question until I've sorted this.

I had been launching them without the developer options visible, I use view -> macros -> view macros -> run. However, I did make them visible yesterday to try some of the suggestions but it doesn't make a difference.

I run dual screen at home and work but the Excel 2016 machine I tested yesterday was a laptop with just one screen. No difference.

One thing that I have just tried is writing another macro and that runs happily without opening the code window so I'm starting to think it's something in the macro itself. I might try cutting it down bit by bit to see if that changes anything.

This would show the editor -

Application.VBE.MainWindow.Visible = True

Have you something like this?

Or have you recorded any keystrokes?

Food for thought thanks. I'm guessing the opposite of that command might force Excel to do what I'd like.

I will have recorded keystrokes as part of the writing process. As I don't tend to write macros very regularly my working practice is generally as below...

Start to record a macro,
Do some stuff with keyboard and mouse roughly related to something I'm trying to achieve
Save as a macro
Write loops and ifs etc around the resulting macro code.

If I come to something that I don't know the command for then I'll generally repeat the record process and copy and paste the resulting code into the main macro that I'm writing.

So yes, there will be keystrokes recorded all over the place.