You'll need a new OCX to deal with all the Service-y stuff,
either ServiceMill.Ocx from Active+ (http://www.active+.com)
or NTSvc.Ocx from Our Friends in Redmond.

Then you just have to tweak your existing code to do the starting
and stopping stuff in the Events provided by the Control, remove
or replace any dialogs, MsgBox's and InputBox's and error trap
'til you're blue in the face.

Simple, really.

HTH,
    Phill  W.

is just what the doctor ordered! I've used it for years ...

--
_________________
Franz Dullaart
TENET
021 686 6010
083 718 1946

 URL:http://msdn.microsoft.com/library/en-us/dnolectrl/html/msdn_ntsrvocx.asp

 URL:http://support.microsoft.com/default.aspx?scid=kb;;q175948

Make the actual "service" as small as possible and break the "real"
functionality and any controlling GUI out into separate components.
That way, the "service" won't ever crash or hang, but if the "real"
workhorse ever does, the "service" can just restart it.