>George,
>
>I agree. However, I know that there are controls out there that work with VB but not with VFP. I don't profess to understand why, but I would guess that they are perhaps not following the programming guide presumably published by MicroSoft. I know that's why we have had problems with Windows programs in general in the past.
>
>Dana
>
I think that those sort of controls might be able to be broken out into two categories: the ones that won't work under VFP, and the ones that are perceived to not work because of differences in the property sets. A graphics control might require a device context, for example. A VB form has this as a property, while VFP does not. That doesn't mean that the package can't be used with VFP, it only means that you have to take the additional steps necessary to retrieve the information.

It doesn't make very good business sense for any software vendor in this area not to try to comply with the standards. It only serves to limit the market potential. I think that, as the technology matures that this will become less and less of a problem.

George