Hello Richard!
Your reasonings behind not using macros for many things is true throughout the industry. They are not difficult to make, but can be time consuming. And planning for maintenance in the future also takes time. It is "the" major objection to overcome when talking with a potential client about a macro project. Yes, they see the potential. Yes, they see the automation. Yes, the ROI is excellent, ... but.
But these objections are no different than those received from work targeted to be written in another language ... like Visual FoxPro. Macro Express has grown in its capabilities. Business wise, we treat it the same as any other high-end language. This comes across as a good thing to the potential client.
It is easier for companies to justify a large macro project than a small macro project. This too, is no different than justifying projects in other languages. Companies just seem to work that way. They can see the forest, but they cannot see the trees.
So, how do we use macros? We conscientiously began Professional Grade Macros by building standard, callable, universal, black-box functions. Sort of a library of external functions that can be used as built-in functions. These are used as building blocks to other, larger functions, which in turn are combined into fully functional macros. It's like a builder. They use the same 8x8x16 cement block in every building built. However, how those same blocks get strung together is the reason why the buildings all look different. This building-block approach is how we use macros. These same blocks of code can be used to build a single family home, or the world's tallest building. They can be used as effectively in small, single-task macros as well as large, multi-task projects.
I won't waste your time by listing all the different types of macro projects that we have worked on. But the diversity of Macro Express needs to be pointed out. It is a magical software package that is not limited to a particular software application, computer, task, or purpose. It is free to do what you want to do. To control what you want to control. To gather data from two different applications and wrap it up with a bow for you to look at while it goes off and does the next thing. Because Macro Express controls applications from the outside in the same manner as you control applications, the potential uses for this magical software package is limited only by what we fail to imagine.
Controlling a computer system by talking to it is fun and exciting. We've come a long way from those belt attached devices that cost thousands of dollars and recognized maybe 200 words ... on a good day (voice recognition devices have been used in the auto industry for years). I wish that I had the time to devote to creating a voice interface to control Macro Express. To build macro libraries. To debug. To test. I know that the software is available today. Right now. And I know it is inexpensive. That is what is so frustrating. When I do get a few moments to experiment, I use IBM's ViaVoice.
Enough of my ramblings ... everybody get back to work ... go out and build a macro