Larry, here is what I am trying to accomplish as time permits.

On a ASP page a user will be asked to enter a phone number. The COM object
I am envisioning will then be instantiated and sent to a provider to determine
the status of the account (call from a pay phone, bad credit, etc). The
connection will be via X.25 not a modem.

I know that one of the future questions will be can I keep this object
always open via a Session object or instantiate it on each call. I have
done a few ASP pages but do not by any strech consider myself an expert.

Looks like I will need to use VFPCOM with BindEvents to accomplish my
goal. Any additional insights you have in this matter will be appreciated.

Thanks for your feedback Larry!

Tom

>>I am in the beginning stages of trying to create a COM object that will be used inside an ASP page. I can instantiate the base MSComm control via the following syntax:
>>
>>oComm = CREATEOBJECT('mscommlib.mscomm')
>>
>< snipped >
>
>Tom,
>As you've seen from this thread OleControl must be instantiated as part of a form. That is a limtiation of VFP. You can instantiate the ActiveX control by itself but you then have to bind it to another object to get the events to run your code.
>
>I'm interested in the reason you are tyring to to do this one aspect. If this is going to be used in an ASP page, what will it do. AFAIK, if the object is created at the top of the ASP code page, the object will be released when the server finishes processing the page. What code could run in that small a time slice? Are you going to instantiate this as part of a session and store it in a session variable?
>
>If you can't tell me. I understand. I'm just curious.