>>I've run into the problem where if you update the OCX, any existing controls of that type should be deleted an re-done. I can't find anyway to do this progammatically. Apparently, code is stored in the VCX which is used by the control (initialization?). Simply put, the only way I've found around this is to do it manually.
>>
>>On the user end (with networks). I'd suggest that the controls be kept in a network directory, and a utility to compare existing ones in the user's system directory and those on the net be used. If there's a newer version on the net, copying it into the system directory (and as a safety measure, re-naming the old one first) seems to work just fine.
>
>Unfortunately this DIDN'T work with the MSCOMM problem. I actually had to find the correct one on my laptop. However, I heard (haven't confirmed) that the latest VB version worked OK with VFP.

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.