Use of invisible window in Service Application to Process Messages

Referring to E-Exchange Question: [Datamodule and handle], I have tried repeatedly to get this example to work in an embedded situation without success.  The example is a standalone program.  I want to solve the same problem as stated in the above referenced question with the addition of an additional feature.  I need to be able to post/send a message from a DataModule that can be processed asynchronously by any other block of code.  This is all happening in a Service Application so visual Forms/Components can't be used (at least so I am told).  When I try to embedd the example above Delphi treats the unit as the program entry point and the Fake Window's event loop gets executed and no other code runs.  I know I am not understanding this, but I've read every other Experts-exchange article I can find and nothing addresses this problem that I can discover.  In case there is another solution strategy that I am also missing, let me explain the exact nature of the problem:

The service comprises a DataModule with ADO and APRO TCP components. It listens for incoming connection requests to log data.  The nature of the APRO TCP component is that it throws an event on a request to Accept an incoming connection.  Because of the nature of the APRO component, processing time spent in the Accept Connection Event code must be kept to a minimum.  The suggested strategy to address this is to create a Custom Message and MessageHandler and to have the Accept Event code post a message to this handler so that the AcceptConnection Event code is released.  This works fine in a visual Form environment but fails in the Service Application.  Hence the initial interest in Sending a message i.e. getting a Handle for a DataModule and subsequently in pursuing the Example referenced at the beginning of this question.  The one constraint I have is that the APRO TCP component MUST be used so please don't suggest a solution using and alternate TCP component.  My company requires that we use this component.  Otherwise I am open to any method that allows expedient exiting of the Event code and asynchronous processing of the handshake for the Connection request.  Thanks in advance for the patience required to deal with this question as I am in now way an expert in Delphi and it's Window/Message/Service structure.