>>>I am trying to use the Winsock Active X object and it worked fine on my computers, but one of our managers computers' displayed an error message that the OLE object is not registered or something to that effect. Is he missing a certain .dll or .ocx needed for this? Why would this active X object only work on certain computers?
>>
>>How are you implementing the Winsock ActiveX control? Did you drop it on a form and distribute it that way? Or did you distribute code with a ox = createobject('mswinsock.winsock') in it?
>>
>>The first way should work if the control is present and is registered. The second way won't work. See MSKB#Q192693 for an explanantion.
>
>I used the active X OLE object from the toolbar in the form. He does have the mswinsck.ocx file, but I did notice that the modification date is earlier than the versions I have. Normally I would code to check the modification date and if it was less than the one in my new user install directory, I would replace it with the new one, but I am thinking this will be a problem to do with an Active X file because they are registered items. I want the code to be user friendly and adapt, is there any links to sites or anything like that where I can have the code automatically link to download a new version install for the active x component (which would register it as well) when i find the ocx with an old date or not exisiting?
>
>
>
>wouldwould also

Kevin,
InstallShield Express, that comes with VFP 7 and 8, uses Windows Installer technology. WI ensures that older versions do not overwrite newer versions of the software. The version you have on your system will be included in the install package. If it is a newer version than the one located on the target system, it will get installed. The necessary registry entries will be made during the installation process.

The Winsock merge module is available under the Objects/Merge Modules section.

HTH.