Thanks John
This is not Frontpage PWS, but another variant of Microsoft PWS. My development machine is currently running Win 98, not NT4 Workstation. I have to say that the PWS has served well so far. All my ASP/ADO pages have worked as expected.
This is my first use of VFP automation from ASP and the server is functioning fine, the dll just remains loaded. Tomorrow, I will load the com server on our NT/IIS server and see what happens.

Thanks
Bill

>When you say PWS, is that the Frontpage PWS. If you are on NT 4 Workstation, IIS in that scenerio is also called Personal Web Server. It is a bit confusing. If it is the Frontpage variety, purge that from your system ASAP. For content, it is ok for dev purposes. When needing to invoke scripting and/or components, it falls way short...
>
>>Hi John
>>Yes I have stopped and re-started the web server, with no success. The web server I am using for development is PWS. Possibly, when I move this to IIS it will no longer be a problem - still it would be nice to be able to develop on a machine using PWS.
>>
>>Bill
>>
>>>This really sucks...doesn't it... This has been a problem with VFP servers. 6.0 improved this. SP 3 I suspect, is even better. I bet if you host the DLL in MTS, you might not have this problem. As for rebooting your machine, have you tried stopping and restarting the web server instead?