> > > > > > It is not only our app that saves .tmp files on that temporary folder. Other apps as well including the OS. All use the same temporary folder for their temporary files needed to operate properly unless you specified another temporary folder for your VFP app like what Borislav says then you can be sure that the .tmp files there really comes from your app alone.> > > > And also if you are using my ssToExcel class, then you should also watch out for .xls and .xlsx files inside your temporary folder because I use that to create a temporary worksheet.> > > > > > http://sandstorm36.blogspot.com/> > http://weblogs.foxite.com/sandstorm36/default.aspx> > http://www.coderisland.com/forum/viewforum.php?f=10> > I guess .tmp files would be in use by running apps. If they can be deleted, they are not in use. I do usually put vfp temp files in a separate folder.> > Mike Yearwood> Microsoft MVP Visual FoxPro 2008, 2009> We have enough youth. We need a fountain of smart!> There may be many ways to skin a cat, but there are very few right ways to do it.

Yes they are. I just tried tracing some earlier to see which creates a tmp file. I deleted everything there then opened excel, it does not create any tmp file so I opened Photoshop next. It creates a temporary file but without any extension, just named it tmpxxxxxx or something. Then I traced one (via Unlocker) that explorer cannot delete and it points to Chikka Text Messenger (a free software in the net where we can send SMS to our mobiles back in the Philippines for free) which is currently open.

I believe that when RAM runs low, it also creates tmp files as swap files.

However, not only running apps creates tmp files. When you install something, some creates tmp files as well. Some automatically deletes those after installation is finished, some apps forgot to.

But there certainly is a good point in deleting tmp folder contents once in a while. I just encountered something weird last week on one unit for Purchasing where my BizCore ERP is installed. Only on that machine a module suddenly generates an error. To make the story short, I tried logging on as a different user and it does not have a problem so it is tied up with a local OS user account, and with local user account, I presume its own tmp files. To test my theory, I came back on that user account, tried running my app again, got the same error; went inside local user's tmp folder and deleted everything there, ran my app back and problem is fixed.