Update: Worked on this all week. Thought it might have something to do with the ocx driver not liking session0, which is where I believe it would run if started by the local service. Tried Powershell and psexec to get it to start in session1 or session 2, both active sessions when running the service. Same results. If I run the same commands in powershell, it works perfectly. Anyone? Please?

Update: Today I tried changing the windows service from "local service" to "network service". No change. Same result. Same event error.

Ok, another strange occurrence: The app runs on the client's server from a command prompt but not from a service I have installed which calls it. The service calls about 28 other programs without an hindrance or errors. When the service calls this app, nothing happens and the server application event states "Faulty Module Path" and lists the path and ocx file located in the same directory as the application's exe file - yet it runs from the command prompt?

This may be less to do with the resource type and ID and more to do with how the program starts on the server. I'm still lost as to why it runs from the command prompt and not via the window's service which calls it?

Any thoughts or pointers in the right direction will be sincerely appreciated.

Additional note: I have unregistered the ocx from the windows registry on my Win 10 and on the client's server. I have removed the ocx file from the SysWOW64 directory on both machines, with the application working on my machine and still not working on the client's server.