I was using the term "Run-time properties" to refer to the "Run-time Object Properties" that you can view when you use the Spy utility and select that option with the radio button.
Regarding erroneous information, I didn't post here to diss the class, I posted in hopes of getting info from experienced users. But since you asked, one example was when he said that I couldn't use Index in programmatic descriptions of objects if QTP's Spy utility didn't report it as an exposed Test-object property. Several experienced people here have used Index, so I thought I'd try. I used one of the sample apps and put a little loop where I incremented the index on a 'webedit' object. Sure enough, it worked well in finding the various objects even though the Spy did not identify this as an exposed property.
Now, back to the original question: Do you folks use Run-time object properties to identify objects?
If the test object methods and properties available for a particular test object do not provide the functionality you need, you can access the native methods and properties of any run-time object in your application using the Object property.
I believe that most of QTP developers are using Run-time properties.
One of the examples:
if Browser("Browser").Page("Page".Webedit("Username") .Object.title = "Username:" Then
We are using descriptive programming approach and in that for identification of the object we will use object's runtime properties only...
so i don't think there is amy problem if we use runtime properties to identify the object