Thanks Claude - I have not yet run anything from ASP.NET so it will be a learning process for me. As far as the app design goes, it is the same vfp mtd.dll that is being called from different pages. Each page calls a different method on the same mtd.dll, or the same page will self-submit, calling a dll method with different parameters based on user input into the pages form controls. I just tried running these asp pages on Win Server 2003 and got mixed results. Not as many temp files were created - only 2 per session. That's the good news. The bad news is that the temp files were orphaned, and not cleaned up when the IIS service was restarted.

Thanks and regards
Bill


>Ok, let me know if you need help running from ASP.NET. If you don't already know, you'll need to run TLBIMP over your vfp mtdll creating a dotnet proxy dll. VS.NET will do this automatically, but you really only need the .NET Framework 1.1 or above(Free) and the dotnet SDK(Free). ActiveVFP does all of this automatically in the background.
>Regarding the design of your app, is there a good reason for having a vfp mtdll for every page? You could design 1 vfp mtdll that has a CASE statement that controls the flow of the application. The URL would look something like this for each call:
>http://localhost/avfpdemo3/default.asp?action=sessionlist
>with the action part being checked by the CASE statement. This is how ActiveVFP is set up...
>
>>Hi Claude
>>Thanks for taking a look on your setup. This is part of a web application. Each asp page creates a single mtdll, uses it, and releases it. So for every page hit one of these temp files is being created. It doesn't seem like it would take long to accumulate a sizable number of temp files. If they were being deleted when the user's session ended, it would not be a problem, but they aren't. They aren't deleted until IIS is restarted. I suppose I could schedule a daily restart of the IIS service, but I would rather eliminate the problem some other way. I will take a look at the behaviour of the same mtdll's under asp.net.
>>
>>Thanks and Regards
>>Bill
>>
>>>I checked c:\windows\temp and it was there after running ActiveVFP in ASP mode and it behaved the way you describe. I'm testing using VFP7SP1 and XP Pro. However, I called the same VFP mtdll from ASP.NET and it didn't create the TMP file at all(after restarting IIS). I guess that's another reason to call the mtdll from ASP.NET??
>>>I'm not sure exactly what it's doing in ASP, but, I would guess it's some sort of cacheing going on. What is the problem with this exactly? Are you creating/destroying multiple VFP mtdlls in your ASP page and creating many Temp files?
>>>>Hi
>>>>Using VFP6 com servers from asp pages. For every vfp com server instantiated on an asp page, a temp file is created in the temp directory. The temp files are 7k in size in the format "????????.tmp". They are created as soon as the com server is instantiated. The problem is they are NOT deleted when the com server is released on the page. They are only deleted when the iis service is restarted. Apparently the creation of these files have something to do with the vfp servers running under the iis process.
>>>>These temp files are created no matter what VFP com server is created on the page. I tested this by creating an empty server based on the custom class, and a 2 line asp page that just created and then released the server, and the temp files were still created and left behind. I tried running the server as an MTS package and the problem was still there.
>>>>How can I prevent this? Has this been fixed in a newer version of VFP?
>>>>
>>>>Thanks and regards
>>>>Bill