Microsoft Excel Error: "There was a problem sending the command to the program."
For the last three years or more, I’ve been living with a little annoyance with Microsoft Excel. It’s one of those things that’s just not quite annoying enough to get to the bottom of, and I figured it was some obscure registry setting I’d never find and must be something odd about my laptop setup only. Sure, I tried a few times to fix it, but I never got anywhere.
Well, today as I was moving from the laptop I’ve been using through the last three years to my brand spanking new HP Envy 15 (more about this bad boy later), I got the dreaded “There was a problem sending the command to the program.” error on the new machine. Ok, now it was personal.
The error occurred anytime I tried to open an Excel file from outside Excel by clicking on it in Windows Explorer or an email. It can look like either of these two examples:
The bottom line is that while the Excel application opens just fine, it doesn’t open the file, showing the error instead. (“Was this information helpful?” No, not so much.)
Off to the Interwebs, and I finally found a post in some obscure forum (three or four reboots later, I have no idea where it was) that gave me a clue about the cause. There’s a setting in Excel 2007 which prevents it from opening files if the request comes via Dynamic Data Exchange (DDE), and it is enabled by default. Go to the Office Button / Excel Options / Advanced, and scroll all the way down to the General section. There you will see the “Ignore other applications that use Dynamic Data Exchange (DDE)” setting checked. Uncheck the box, click OK to apply, and you’re good to go. Never mind that those very applications that want to use DDE may be other Office apps!
<UPDATE dateTime=”2011-07-21T16:48″>If you’re using Office 2007, the Office Button is the big circle with the logo in the upper left of the screen shown above. If you’re using Office 2010, there’s no longer a button, but what’s called “backstage”, shown below.</UPDATE>
First time I see this error myself, but thanks to you I won’t see it again! You just made my day a whole lot easier, thanks Marc!
Fantastic! Worked instantly
had a client with this problem today and your resolution fixed their issue. thanks for posting! I will keep this one handy for the next time :).
Thank you! Solved my problem.
thanks it saved my time
thanks a lot.
AK
For me, it turned out the DDE was not my issue. I was running an add-in called BeGraphic(http://www.begraphic.com/). It allows me to create dial indicators in reports. For some reason, it started throwing this error. When I disable the add-in, problem solved. But, I still need the dials (my boss just loves them, even though I think they are tacky). I’m going to try un/re-installing the add-in.
Thank you so much. This solved my problem.
Thanks for the help solved the problem in 2 seconds!
wow!!! I have been living with this for a few years also and truly haven’t made the effort to fix it, but it bugged me alot~!!!!!! Thank you for Blogging about this.