Problems using Index/Location
We have a problem with identifying some ActiveX components, so we have to use index or location to do this.
And this works fine if we have all controls visible at the same time. But we have some windows in our application that only shows one of these ActiveX components first, and then later showing the rest of the components.
When only one of the components are showing, the component will not be recognized with an index or location. But when all components are showing, then they will have an index or location property in Object Repository.
We have tried to add the index property as mandatory property to the ActiveX in object identification, but this property still did not get any value when only one component were showing.
So for now we have to add 2 objects in OR for the same component in our application, but this is not what we want to do.
Does anyone have experience in solving the same or a similar problem ?
Re: Problems using Index/Location
QTP does not work on hidden objects and it uses index only when non-hidden objects are present and more than one object matches the given description. Index can never be made a mandatory property it will always remian as an Ordinal identifier as per QTP architecture.