NameMapping, Mapped Objects & Aliases - 101

Thanks Curt, that's what I was thinking that the only real way around this is to use Find, FindChild, etc.  It does pose a few issues though. First, it kind of defeats the purpose of the NameMapping file.  Second, there may be multiple things that I want to do to an object.  For example, in a combo/list, I may want to select one, multi-select, right-click, etc.  I only see two options in doing that:  create a function that describes the object and performs many different operations on it, thereby making it a much larger function that it needs to be, or create a single function for each operation with  he description being the same in every function.  Either way, it's more difficult to maintain, and you have to be careful on the test setup in the way that you call the functions.  Hmm.  Too bad that we can't somehow describe the objects in the NameMapping file in such a way that it doesn't matter where on the application it's located.  That way the test will not break when things are added or deleted.