>We have a com server that has been working well for us for quite a while. It is based on Rich Strahl's general recipe for foxisapi applications. The development work was done on a different computer than the web server, so we have to register the com server when we get it over to the web server. We Used to "comservernam /regserver" command to register the application. Recently we began work on a new com server to handle a batch of very different tasks. Instead of including the procedures in the first application we decided to go with a different application. When we register the new com server application, the old one ceases to be available to foxisapi calls. We deployed the new app in the same folder as the first. The first server has an exe name of "foxweb". The class definition is: DEFINE CLASS server AS CUSTOM OLEPUBLIC. The new server has an exe name of amlweb.exe and a class definition as: DEFINE CLASS amlserver AS CUSTOM OLEPUBLIC. Yet the regserver command seems to
>be overwriting whichever com server is already registered. Help.
>

IN addition to what Jon and Craig said, ensure that one project hasn't accidentally included the class definition for the other one, compiling both classes in the same dll.