Fair enough. :-)
I think I would have to concur that using multiple aliases to map to the same object is a relatively unstable method of doing things. I've found similar problems but not necessarily in the fashion you're trying to implement. What I did, though, was use a single alias but use Conditional Mode in the NameMapping node itself to say that, for example, your button could be mapped to the node if the WndCaption is either "Next" or "Finish". That way the button is always consistently found no matter the specifics of it.
It think that is keeping in with the stability of the TestComplete application. While it allows you to map the same thing to two different aliases, in my mind, an alias is a unique identifier for an object. So, a Many Alias to One Object relationship doesn't work well. However, a One Alias to many Objects using Conditional modes, wildcarded property values, and other similar techniques, works well and is stable.
