I disagree,
Error protection, is standard procedure.
Sendkeys Is fairly reliable, although fussy, but when used correctly is ok. If there is an error the sendkeys fails, and I dont get a lockup. Maybe due to the DoEvents which flushes sendkeys.



Microsoft Press encourages sendkeys.
"You now have all you need to run an external program, and interact with it"(Balena MS)


SendMessage APIs are limited, compared to sendkeys.
They actually both have some advantages, and disadantages.

Bad points for sendmessage:
Some external applications, use their own sendmesseges syntax.
More complicated, as referenced by Balena.
More mainstream, so slightly more likely to be hacked.
I think some character combos, that are easy with sendkeys, take extra work to be input, with sendmessage.

Bad points for sendkeys:
Some external applications, don't allow tab focus on the control you want,(for sendkeys) and or dont have a keyboard friendly, user interface, for control of the menu, and controls.

Good sendmessage:
You'll have to learn it eventually, so why not start now.
Robust and predictable. Granted!

Good sendkeys:
In the here and now, this is simplistic alternative to sendmessage.
If you have VB.net, you can alter the external application file, so that focus can occur on any contol you want!!! This negates a bad point.


Please add more!