Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Mscomm32 and c++ ver 5.0
Message
 
À
24/07/1997 10:35:18
Nico Grilli
Spark Consulting Srl
Corato (Ba), Italie
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00038339
Message ID:
00041491
Vues:
44
>>>>>I have just installed c++ ver 5.0 and I discovered that among other things my mscomm32.ocx is update to a
>>>>>newer version. And this version does not function with my VFP 5.0???
>>>>>
>>>>>Is there anybody how knows this??
>>>>>I have the following message OLE error code 0x800a018a:Unknown OLE status code.
>>>>>This occure in InBufferCcount,DSRHolding etc....
>>>>>
>>>>>Is VFP 5.0 to old for C++ 5.0 or....???
>>>>>
>>>>>
>>>>>Best regards
>>>>>Per Simmersholm
>>>>
>>>>Hi Per,
>>>>I upgraded to C++ 5.0 also, and had trouble with other .ocx, but not MSComm.
>>>>All of the other ocx trouble was from multiple copys of the ocx's on the disk.
>>>>Had to make sure ALL copies were the same.
>>>>
>>>>Also had trouble between multiple developers, who had NOT upgraded. Also had to update the distribution tree copies of the ocx's where we are distributing .exe files.
>>>>
>>>>HTH
>>>
>>>
>>>i have the same problem...and i have deleted all copy of MSComm
>>>but the OLE Error code is the same...
>>>can you help me?
>>>
>>>thanks.
>>>Nico
>>
>>You have to install the OCX version from VFP CD-ROM again, and re-register it. Similar thing happened to me with comctl32.ocx in VFP after VB 5 installation.
>>
>>Nick
>
>i have made it, but the error is the same.
>I have also installed VFP 5.0 (from Vstudio) on a new PC with only WIN95
withouth any other software...
>...but the error is the same.
>
>can you hel me?...
>...i don't known how i can use MSComm32
>
>Nico
>Tanks

I used the new mscomm32, I just had to copy the new one over the old ones in the distrubution tree I was using for .exe's. Then open the project and rebuild it.
Several other developers, who were working with the same project, had to copy the file to their \windows\system, and then register it.

HTH
Glenn
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform