>>Just one more note on this. From what I can tell, if the file already exists if the version date is equal to or less than the version date of the new control, the extension is changed (to *.oc$) and the new file replaces it. Note, that it's the internal version date of the file, and not the time stamp. Even if the time stamp is later, it gets overwritten. I've seen the behavior first hand.
>>
>>As a side note, if you want to find out what the version date of a control is, you can use the GetFileVersion() function in foxtools.
>
>Thanks for the info, George. One related question, if you don't mind: do you think there could ever be any trouble if, for example, a vfp install overwrites an older ocx that, say, a VB app uses?

Bruce, I left a message just 1-2 days ago about this exact problem. I was using MSCOMM32, and a newer version was installed with a VB update. All of sudden none of my properties were editable. It took a LOT of work to figure out why my laptop still worked and my regular computer didn't!

I now have a backup copy of the 'right' version.