It's not clear from your post what the problem is.
Take a look at

- file #9336 Basic Serial Communication with MSCOMM
- file #9636 Good practice in using MSCOMM.OCX in VFP
- faq #7807 Serial communications with a COM port using MSCOMM
- faq #7943 How do I determine the Comm ports available to MSCOMM

>Hello,
>
>I am not at all familiar with Ole controls in VFP but I have to
>enable a RS232 port on a PC to do some serial transmit and receive.
>I searched and read the following article and was ready to try out
>the samples codes suggested in it.
> Microsoft Knowledge Base Article - Q139526
> HOWTO: Send to the Serial Port by Using Mscomm32.ocx
>At the end of the article I noticed its mentioning about a possible
>error when running an app containing the same syntax created using
>the setup wizard. I tried the sample codes anyway and indeed the
>error message was generated. I went on to check the Micorsoft
>Knowledge Base article Q192693 BUG:
> License Error with ActiveX control add at run-time.
>This article suggests a work around but I must admit I couldn't
>get too much out of it due to my limited knowledge in VFP.
>I am trying to get all the help I can get- the kind of help that
>I understand; and even thinking of upgrading to VFP7 (I am using
>VFP6.0 with SP3) if that would save me the trouble.
>
>Does anybody knows if this error had been fixed in any later
>versions of service packs? Or is there a more direct way to
>fix or get around that problem? If VFP7 was to be used to build the
>app with the same syntax, will there still be errors?
>
>Could anyone who experienced this be kind enough to give me
>some directions? Thanks for any help.
>
>Jang