As you can see the pros and cons of breaking or maintaining project compability are there. If you break compatibility, then you get to see your new code running immediately. However you need to change the project name & save it with this new project name. You also need to change the project name in your asp pages.

If you prefer to keep project compatibility, then you need to wait -- and for how long? -- for the remote server to be rebooted. But then you do not have to worry about changing and resaving with a new project name.

If you follow the instructions closely, the whole thing should work and for NT server. I have not tried it on a Win2000 server and so do not know whether it will work on it.

As a closing note, if you are not familiar with ActiveX DLL you will find on this StarDeveloper website an excellent tutorial written by Faisal Khan. That will get up you up and running on migrating your ASP pages to ActiveX DLLs. But before you rush into it, be aware that an ActiveX DLL once registered on the server can be used by other websites hosted on the same server.