Hello,
"CreateObject" run a combination of code on the client side (in this case, the Xbase++ code for it), and a code of the component itself (if it successfuly manages to connect to it). Therefore the problem can be on either side.
I have some questions:

Have you waited "long enough", i.e. isn't there actually some error message, but after a long time? I am asking because the function needs to start a separate process and wait before it registers its class factories with COM, so there is a wait operation inside Microsoft COM that is supposed to eventually time out if not eveything goes right.
When your code reaches the "CreateObject", can you actually see the "easyopcl" process starting in Task Manager? If not, then this a client side or service/COM configuration problem, because our code does not get a chance to run. If, on the other hand, our process is starting, we will need to investigate further in this direction.

Thank you

Hello,
for current instrucions to registering the component as a service, please see the main "Concepts" document (installed with the product, or <a href="www.opclabs.com/LinkClick.aspx?fileticket=HnhVghOf-Cc%3d&tabid=217&mid=988" target="_blank" rel="nofollow">www.opclabs.com/LinkClick.aspx...), and look for the "COM Registration and Server Types" heading.
In general, all combinations are possible (your application as an application/a service, and EasyOPC component as an application/a service), but they may require different settings - especially around security. The security is also most likely the cause of your problem. Services run under accounts they are configure to run in Service Manager; and, if they are DCOM components, they are influenced by the settings in DCOMCNFG. It is is necessary to give permissions to proper accounts to launch and access the component - and the OPC server; and, in fact, also your client - because the component is making callbacks (if you are using subscriptions).
For start, we need to know what kind of error are you getting?