When using office suites from Microsoft, quite often you can come across a situation where an error occurs when sending a command to an application. Please note that this failure is mainly and exclusively related to the MS Office software package, and in general does not have any relation to the operability of the operating system itself (with the exception of only one case, which will be considered separately). But what is this failure? Let’s, as they say, dig deeper into the desired problem.
Error directing the command to the application: how to understand this?
What is most sad: this failure is typical only for two editors - Word and Excel. The first is a tool for processing textual information, the second is a tool for working with tabular data.
But why, then, the error sending the command to the application does not appear in the same Access applet, which for the most part operates with database data? Everything is simple. Apparently, editors simply cannot read the information contained in DOCX and XLSX files, which are adopted as the default standard in later versions of the Office (documents like DOC or XLS in later versions must be opened exclusively with a change in the file type in corresponding menu). These are templates that should be opened initially, but not adapted to perform such actions.
How to eliminate the error of sending the command to the application by the classical method?
But there is a way out, the easiest one. The error in sending a command to an application in Word is completely solved by reopening the file you are looking for.
If this does not help, when opening, you should get rid of the so-called DDE queries, which ignore compatibility mode. The solution to eliminating the error in sending the command to the application in this case is to start the desired program in compatibility mode with the previous, and not with the current operating system. In most cases, this helps. By the way, in a similar way the problem of when the error of sending the command to the application in AutoCAD appears.
To fix the failure, you need to go into the most common “Explorer” and use the installed program files directory Program Files and the folder of the applications you are looking for (for example, Office with a choice of the appropriate editor's directory).
There will be an executable startup file (for example, Word.exe). It needs to be used (or rather, its launch properties).
Through the PCM menu on it, go to the properties, and then from the drop-down menu just below select the launch point in compatibility mode, say, with Windows XP.
Excel Solution
For this editor, the above solution is also suitable, but you can offer more cardinal ways.
The error in sending the command to the Excel application is eliminated so elementarily in the program itself that it is impossible to imagine. To get started, use the "Office" button, located at the top left, then select the Excel options item and go to additional options. It is here that you need to uncheck the line for ignoring DDE requests. When the configuration is completed, save the changes directly in the editor, close it, reboot the system, and then try to open the file with the problems.
What does TuneUp have to do with it?
Another reason that the error in sending the command to the application appears on Windows is due to the use of the TuneUp applet. It is a bridge for connecting "apple" mobile devices to Microsoft systems. It is not surprising that competing corporations insert their bugs into all software products.
In this case, it is recommended to get rid of this utility completely and completely, using for this purpose not system tools in the form of a standard section of programs and applications, but uninstallation utilities that can not only delete applications in the usual way, but also look for residual garbage in the form of file system registry entries and folders. The iObit Uninstaller program can work perfectly, the free version of which works with almost no restrictions.
Registry Actions
In the most cardinal way, the error of sending a command to the application is eliminated through the registry, but you will have to perform such actions at your own peril and risk.
Call the editor using the regedit command through the Run menu and navigate the HKCU branch through the directory tree to the CurrentVersion directory. In it, you need to delete all the contents, then exit the editor and completely restart the computer system. It is possible that such a method as the latest solution will give its result.
Keep in mind that it will not be possible to undo the changes made in the registry, because they are saved automatically, so before the intervention, take the trouble to at least create a backup copy using the appropriate item in the editor itself, the system section or the parameters of the optimizer program in which such a module is available in stock.
Instead of a total
Actually, as you can already see, the error itself is not particularly critical. It may well be that even installing the latest service packs specifically designed for office suites will fix the problems without outside user intervention. To do this, simply check their availability in the Update Center by specifying a manual search. If this does not work, use the Fix It utility, which can be downloaded directly from the official Microsoft resource, or use registry cleaners and optimizer programs that can find and delete obsolete, incorrect, or empty entries. At the same time, manual intervention in the registry is excluded completely and completely (and for many users of the initial level of training it is undesirable at all).