>>>Thanks for the tip! I still need to figure out why my MSCOMM properties show "OLE error code 0x800a018a: Unknown OLE status code" Any ideas?
>>
>>Larry, did you ever solve this? Yesterday I found all my MSCOMM properties were now reading OLE error code 0x800a018a like yours - but only on 1 computer. Move the form and the properties had strange values but could be changed to the correct version.
>>
>>Do a search for ALL copies of MSCOMM32.OCX. I'd had a newer version installed by new software. I changed it back to the old VFP version and re-registered it, and I'm running fine now. When I have time, I'll see if I can 'upgrade' to the newer version. (version that is working: 8/21/96, 12:00am)
>>
>>HTH
>>Barbara
>How do you re-register it?
>p.s. thanx for the tip! //:^)

Larry, just use Regsvr32. Choose RUN from the start menu and type in

REGSVR32 C:\windows\system\mscomm32.ocx

Add path to Regsvr32 if necessary. Probably windows\system or your local equivalent.

By the way, I found the correct version in my distribution disk file. You may have to go to backups if you don't have distribution disks of your software. Will keep you posted if I can make the newer version work.

I have now made copies of ALL the OCXs I'm presently using in VFP. Zipped them up and stored them in a subdirectory under VFP. Did the same on the laptop, which is less likely to be involuntarily upgraded by new software.

Barbara