>Don't use the init of the objects to do much. Create your own Setup method on oSock and oHandler. Instantiate both oSock and oHandler within oxServer's Init and call their Setup methods. oxServer should have methods to support communication between oSock and oHandler. oxServer should have a method like GetState and GetAcknowledgement. oSock should have a method like GetState and oHandler should have a method like GetAcknowledgement. oHandler.GetState can then do THIS.Parent.GetState().
>
>My telephone handset has a jack for a headset. The jack is like oxServer. It connects the headset to the handset. The blueprints for each contain the details for each AND they show single connection points between each.
>
>Each of these don't know anything about the other except the connection points.

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.

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)