| || |
Why do parent objects also need to be mapped name?
I select a object property to be mapped a name, and then appears a listing of parent objects (all the way down to Sys object and iexplorer object). In my case, I have about 8 parent objects.
Why do I need to name all these parents? Can not I just name the child, and the tool remembers it's parent?
Re: Why do parent objects also need to be mapped name?
Parents need to be mapped, because Name Mapping builds its own object tree in which parent-child relations are preserved. However, you can create an alias for the needed object (just clear the Aliases pane and drag the needed object there). This will allow you to address it like 'obj = Aliases.MyObject', no matter how many parents it has (see the "Name Mapping Aliases" help topic).