Neil,

Let me preface this by I'm not an ASP or MTS guy...

You instantiate an EXE com server that same as you would the DLL. As an EXE server the COM calls take a bit longer because of the context switching the CPU must do to switch between the two EXEs. This isn't really an issue unless you are trying to make hundreds of calls per second.

ox = CreateObject( "ExeNameHere.OLEPublicClassNameHere" )

Then I'd try this

ox.Visible = .t.
ox.DoTheThingYouDoSoWell()

You can in fact experiment with all of this from a VFP session without involving the ASP. Once you've got it working from VFP move the code over to the ASP page and give it a try.

>I thought that it was probably the UI of the EMODEL.exe. You are correct about the dll. I am using a com server on the ASP and it is a multithreaded dll com server. I recompiled the project as an exe com server and registered it via :
>clicking on START-> RUN d:\vfp\distribute\desktop\ecentricsst.exe /regserver
>
>BUT.... I don't know how to instantiate an exe server. In the command window I typed:
>oo = CREATEOBJECT("ecentricsst.geodigmevents") and I got an error that the class could not be found. Therefore, before I can investigate your first suggestion please walk me thru the instantiation of ecentricsst.exe as a com server.