>Ed,
>
>Then it sounds like MS needs to get busy and get the API integrated and supported in VFP. I'm going to post this to Microsoft in the MVP newsgroup.
>
>Does setting Sparse=.F. in the grid coulmns help any? Does Jaws actually work with VFP controls outside a grid? If so it sounds like the API is at least partially supported by VFP.
>

No, it doesn't. It is an issue involving Active Accessibility support, and the degree of integration found between VFP controls and the Windows Messaging system. FWIW, VB is not a panacea for this situation; some VB controls are well-supported by Jaws, and others are not. It's just the there's more of a likelihood of finding a fully-supported control of a given type for VB given the wide range of third-party controls available to VB programmers.

If things are changing much in VFP 6/Tahoe, then I'd venture to say that MS will tell us all to wait until it's released; they aren't going to go back and redo 5.0's screen objects from thr ground up at this point.

>>They aren't a great deal of help here, and I suspect that your reasons are quite correct from having dealt with the product in the past. Jaws works through the Active Accessibility API, linking into the Windows display system as a Windows message interceptor.