>There is an ASP that accesses a vfp com object, but doesn't appear to release it, so when I try and re-build the DLL it keeps saying it's in use. Using PWS.

If you're developing on PWS, I wouldn't do my testing or debugging as a COM using ASP. Test as a regular VFP class first. Than test it out as a COM object. When you're confident in its behavior, then load it up in the ASP.

PWS keeps your COM in use just like IIS does, but while Windows 2000 has nifty stuff like COM+ and IISRESET.exe, I think that the only way to unload your DLL is to reboot Windows, unless you have MTS.

If you're doing Web Server based apps like this, I would strongly consider getting a Windows 2000 or XP machine to do it on.