There are a number of instances where QTP shows inconsistency on recognizing object properties. When an object is added to the Shared Object Repository or an object is added via recording, we will see a number of object properties get stored along with their values.
On playback, these objects are recognized and QTP works just fine on several iterations. Then suddenly QTP can no longer see the value of a particular property and just fails on it. Eliminating that property from the repository is usually not an option because the other properties are insufficient to establish unique recognition (meaning that there are other objects of the same class with the same values for the other properties)
Why is this inconsistency happening?
Is there some configuration in object recognition or object identification that can alleviate this problem? We are working with a Visual Basic 6 application in a client server environment and I am using the Visual Basic Add-In only. No other Add In is loaded or enabled.