>>>Larry, I've been setting properties in the MSCOMM32 (VFP5) with no problem by right-clicking on the OCX in Form Designer. Also, many (not all) of the properties are in the standard VFP property sheet.
>>>
>>>Barbara
>>
>>1) With the properties window open do some of the properties show "error" in the values?
>
>No, all of the properties show values (or blanks)
>
>>2) I set up a form containing an MSCOMM object and show the MSCOMM properties using text boxes with the control source tied to the properties and an OK and CANCEL/QUIT command buttons. When I run the form to test, it acts like it locks up. Even though I set the focus to the OK button, nothing activates. When I put a "set step on" in the form.activate button, I can set the properties with no problem from the command box. What do you think I may be doing incorrectly?
>
>When you run the form with PortOpen = .T., you automatically set the MSCOMM object "On". Do you have code in the OnComm method? It LOOKS like the form is locked up, but it's actually waiting for your COMM port to say something.
>
>Change to PortOpen = .F. and set it to .T. with a button for testing.
>
>HTH
>Barbara

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?