Forum Discussion
AlexeyKolosov
Staff
14 years agoHi Mateus,
You should either mask the variable part of the class with the '*' wildcard, as I suggested earlier, or, if multiple windows with similar classes will match this criteria, specify other, more reliable, recognition criteria for the window. For example, the value of the ControlID property should coincide with the numeric control identifier declared in your MFC application's sources (should be declared in resource.h, as far as I remember). Also, if you don't actually need to work with the problematic window, but need to access its child object(s), you can make TestComplete ignore the problematic object via the Extended Find feature (see the Using Extended Search Criteria for Mapped Object Identification help topic for more information).
You should either mask the variable part of the class with the '*' wildcard, as I suggested earlier, or, if multiple windows with similar classes will match this criteria, specify other, more reliable, recognition criteria for the window. For example, the value of the ControlID property should coincide with the numeric control identifier declared in your MFC application's sources (should be declared in resource.h, as far as I remember). Also, if you don't actually need to work with the problematic window, but need to access its child object(s), you can make TestComplete ignore the problematic object via the Extended Find feature (see the Using Extended Search Criteria for Mapped Object Identification help topic for more information).