I could swear that the start up mode is different when running as a service.

Firstly I was using the the new operator and this worked fine when calling a
running version of the activex.exe. As a service the new operator would
always create a new instance of the exe which is not what is required.

So then I thought about the GetObject method so I have the exe register
itself in the ROT and again this works fine on a running version of the
activex.exe. When I install it as a service using the ntsvc.ocx I then get
an error on the GetObject as if the type doesn't exist. Stop the service and
it works as a activex.exe start the service and it stops?



-----Original Message-----
From: Straforini, Marco [mailto:marco.straforini@c...]
Sent: 31 July 2002 18:48
To: professional vb
Subject: [pro_vb] RE: HELP Communicating to a VB service


Stuart,

I have only one nt service written in VB (all the others
are in C++), and I do not have any problem in connecting to.
Which kind of error do you have? DO you connect using the
New operator or by CreateObject? Is it a local or remote
service? Please tell us what error message you get and from
which line of code.

Marco

-----Original Message-----
From: Stuart Naylor [mailto:indtec@e...]
Sent: Wednesday, July 31, 2002 6:38 AM
To: professional vb
Subject: [pro_vb] RE: HELP Communicating to a VB service


Any Com Gurus out there now what the problem is ?



---
Visual C# - A Guide for VB6 Developers
This book will make it easy to transfer your skills
from Visual Basic 6 to C#, the language of choice
of the .NET Framework.
http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059