So my idea of using analysis.wbt program to create "fingerprints" of the various windows inside the ancient program I'm trying to interact with, kind of worked, but I still have about a dozen or so screens which analysis.wbt produces 100% identical results for, yet have completely different contents, and for most of them I can't seem to "read" anything out of them that is useful for me to know which screen I'm on.
For the record, I'm trying to automate keying of data into this ancient system. So it's critical I know "where" I am before issuing SendKeys blindly as it can have some pretty disastrous results if I'm not where I think I am.
Look for an outside the box ideas to "read" the screen, as opposed to the ususal, window interrogation/properties stuff. I've got no issues getting focus, but it's making sure I know exactly where I am has been the problem.
Any suggestions greatly appreciated, but the normal solutions just won't work here.
Thanks again