Craig,

Frankly I *had* thought that this had been the case for FPW (painted-on controls) but that VFP had gone and "done it right".

Shows you how much I know!#$@!

I feel it is a reasonable wish and, furthermore, would say that they should do it through existing classes - it's their problem to make them comaptible with current classes.

Cheers,
Jim N

>I would like to post a wish list item that a future version of VFP includes an additional set of user interface baseclasses which are subclassed from the native windows classes (text boxes, buttons etc.).
>I am assuming that it would not be feasible to change the existing baseclasses without creating major backward compatibility issues.
>
>This has become an issue for me as the automated testing software I have recently purchased can only interrogate controls that are based on windows controls. In a VFP app it cannot go beyond the form level (except by using bitmap comparisons). (said testing software works like a charm with VB & Delphi apps)
>
>Before I submit this as a wish list item does anybody else have any comments on whether this would be a useful addition to VFP?
>Would there be benefits other than facilitating automated testing?
>
>Thanks
>Craig