>>>As the title states, this is the error I am getting. I found a thread concerning this by searching for mscomm32 but there was no resolution. I have tried registering this component using regsrv32 but to no avail.
>>>
>>>What has changed since it did work is that I got a new computer. The OS (Win95) was reinstalled on the new c: drive. What used to be my c: drive now became my d: drive. I am running VFP from d:. I have reinstalled VFP 5.0 but still now luck.
>>>
>>>Any ideas would be greatly appreciated.
>>>
>>>Thanks,
>>>George
>>
>>George,
>>
>>See the Third Party Products, under the FAQ section of the Knowledge Base here. I had a similar experience, and the resolution was to obtain the license code (which is about a mile, it seems long). If you can't get it from the registry of your old computer, you'll have to contact Microsoft.
>>
>>You have my sympathies. It's a very frustrating experience.
>>
>>George
>
>
>George,
>Thanks for the quick reply. You are not kidding when you say it is a frustrating experience. I give your ideas a try and keep my fingers crossed. Could be in for a loooong weekend now :)
>
>George

I had the same problem and none of the solutions in the KB helped at all. Save yourself some time and call Microsoft first. Tell them first off that you need the license codes for the registry for your ocxs. They should be familiar enough with the problem now that they will know exactly what you are talking about. It took me 4 1/2 hours to get the numbers from them, but believe me, from everyone that I have talked to, this is the only solution. By the way, the most common cause of the problem is the installation of Office 97 or the uninstall of VFP on the machine.