>I've noted in the release candidate of VFP 6.0 that the controls that were generating this type of error in 5.0, no longer do so. My experience is that the promise of better ActiveX integration has been addressed in the latest release. Only time (and experience with other controls) will be able to tell us how much so.

GOOD news. Thanks.