>>A bit of reading seems to suggest that the problem is because VFP UI objects (commandbutton, textbox etc) are not based on Windows controls (? does this make sense) whereas the corresponding UI objects in Delphi, VB etc are subclassed from native windows controls.
>
>You are right here. Unfortunately! :(
>
>>So my questions are ...
>>1. Can somebody give me a quick explanation of the VFP UI objects/classes and how (if?) they relate to the native windows classes?
>
>VFP objects are not based on windows classes, but only painted on screen/forms. This is why you cannot go beyond form level.
>
>This is very easy to see if you use a Spy tool (like Spy++ from MS that is shipped with VC++).
>
>>2. If anybody out there has experience with Vermont HighTest targetting VFP 5.0 applications can you tell me if/how HighTest can be configured to recognise VFP UI objects/classes?
>
>I don't know the product you bought, but if it was not designed to work with VFP, then, probably there's no way to make it work. You must talk with the producer, he is the only one that can confirm/infirm this.
>
>Vlad

Thanks for the reply Vlad.

I would assume this is a "feature" of VFP that will not change in the forseeable future.

Does anybody have experience with any automated testing tools that can specifically target VFP apps at the UI object level (eg: get the current text value) rather than just doing bitmap comparisons?
Can the (formerly) Microsoft Visual Test (?now Rational Test) interrogate VFP UI objects in this fashion?

TIA for any tips.

Craig