I gave up. I just have three classes now. MyBFClass, MyServer and MyClient. I dropped oHandler and create oSock in MyBFClass. I put all the procs that do server-type stuff in MyServer and just simply reference THIS.WhateverProcedure to handle receiving data and processing. I don't like it, but at least I understand it and it mostly works. Got an OLE Dispatch error, but at least that tells me that I'm calling a valid Winsock procedure, just not correctly. I'll have to take some OOP training and then I'll rewrite it someday. I was just trying to do it the right way, but I don't have enough knowledge/experience to do that now.


>Jay
>
>>This is really the layout I have right now. oSock is created in EMPS_Class, but since oxServer is based on EMPS_Class, it should be availabe there as well. Right? I'm playing around with a GetState procedure and just can't seem to find a relationship to oSock.State from within the SendAcknowledgement procedure.
>
>To paraphrase Yoda ... "That is why you fail." :)
>
>Forget about what something is based on. We talk about FoxPro, we don't say Visual FoxPro 9 (based on VFP 8, based on VFP 7, ... based on Foxbase).
>
>You're confusing me with that. :)
>
>Please explain in English what you are trying to do. Use something that exists in the real world as a model. A handler is a guy that works with animals?
>
>
>>
>>
>>

>>EMPS_Class
>>	Create oSock (based on Winsock)
>>		.State
>>
>>EMPS_Handler_Class (just a hook right now)
>>
>>EMPS_Medinotes_Handler_Class (based on EMPS_Handler_Class)
>>	SendAcknowledgement Procedure (needs oSock.State)
>>
>>EMPS_Server_Class (based on EMPS_Class)
>>	Create oHandler (based on EMPS_Medinotes_Handler_Class)
>>
>>