Gary,
Problem solved! Thank you, what a wonderful resource!
Steve

>Steve-
>
>See the post I did today, "[Classes - VCX] Re: COM .dll - and memory release Thread #173368 Message #173446" for instructions on how to set up your web site for this sort of thing.
>
>>Arne,
>> I can't build or delete once they have been loaded. IIS locks them up and I'm trying to find out how to prevent this because it makes for a difficult development environment. Please let me know if you hear any solution.
>>Steve
>>
>>>Steve,
>>>Can you build (or delete) the DLL when you do remember to set oMyserver=nothing?
>>>The reason I ask is that I can not, seems that once it's been loaded from an ASP-page, it's locked until I reboot :(
>>>I'm doing my testing with Personal Web Server under Win'98, so things might be behaving differently under NT.
>>>Arne
>>>
>>>> In NT 4.0 server how do I turn off running COM servers if I forgot to
>>>>close them with
>>>>
>>>>set oMyServer=nothing
>>>>
>>>>>
>>>>>You also have to make sure that the COM server is not running at the time you rebuild the project.
>>>>>
>>>>>>I am experimenting with creating in-process objects in VFP6 that I can use during .asp processing. My problem is that every COM .DLL that I create during testing cannot be overwritten or deleted. This means that I have to save it to a new .DLL each time.
>>>>>>
>>>>>>Is there an elegant way to work with COM .DLL's??