Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
COM object still in Memory
Message
 
 
À
25/07/2000 12:18:46
Information générale
Forum:
Visual FoxPro
Catégorie:
Applications Internet
Divers
Thread ID:
00396650
Message ID:
00396696
Vues:
11
Bob,
IIS caches COM objects in order to use them more efficiently the next time they are called. In order to unload it, at the CMD prompt (assuming NT because you are using IIS), type: net stop iisadmin. It is this service that locks it. This will also shut down the web servirce (also ftp and smtp).

Rebooting should have released it unless this object is accessed as part of the Application_Start event.

HTH.

>I have an ASP page that calls a FOX DLL
>
>ASP CODE:
>Dim strjobnum, strbinnum, oNB, strBinResp
>strjobnum = Request.Form("jobnum")
>strbinnum = Request.Form("binnum")
>SET oNB = Server.Createobject("filmroute.fwip")
>strBinResp = oNB.binjob(strjobnum,strbinnum)
>SET oNB = Nothing
>
>Once this is complete and I try to regenerate the Multithread DLL I get File access is denied. In order to regenerate it I have to reboot my PC which tells me it is still loaded in Memory. Shutting down the COM object through IIS does not help as well as shutting down the web server service. I found an article on this and all variables in the COM object must be PRIVATE which they are. I am woried that I will run out of system resources. Does anybody know why it is still in memory and what I can do to fix it?
Larry Miller
MCSD
LWMiller3@verizon.net

Accumulate learning by study, understand what you learn by questioning. -- Mingjiao
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform