>You don't have to do anything different other than to recompile. An out of process exe is similar to a regular exe in that it can be run as a regular exe, but when the exe is built it gets registered as an OLE server same as an OLE DLL and can be used from another App (such as VB) using "createobject" and then manipulated as an object. The article I stated previously talks about some of the differences between and In Process server and an Out of process server. Essentially the difference is (according to the article):
>
>"An In Process OLE server is simply a DLL that lives in the same process address space as the OLE Client. An Out of Process server lives in it's own process space, and thus is typically an .EXE."

Thanks, as mentioned in Jeff's reply, I made the change and still can call it from Visual Basic. However, it appears and ends immediately.