Ran into one situation where temp folder contained close to 20K files. Despite my initial suggestion to use command line, the tech insisted on using a "less complicated (and faster)" route and spent over two hours after which he gave up (cleaning out about 1/4 or 1/3 of the files). After that, I connected via remote desktop session, got to the command line and did the cleanup in just under a minute.
>I haven't run into cases where the GUI version failed but it sure is long-winded - calculate items to be deleted, elevate to admin if you want to delete, recalculate, re-confirm...
>
>>... and it is not uncommon in such cases to have to manually perform the cleanup (i.e. the "Disk Cleanup" option doesn't always clean the orphaned files). It's also likely in those cases that the manual cleanup would be much faster using the command line than through the GUI.
>>
>>>Some people don't realize that over time orphaned temp files accumulate and need to be periodically deleted. I've seen cases where this hasn't been done for several years, and thousands of temp files have accumulated. In those cases it's rare, but not impossible that VFP might want to create a temp file based on the system time, and end up with a collision with a file that already exists.
>>>
>>>The few times I've seen this happen, I ask the client to check their temp files folder, there have always been tons of files there.
>>>
>>>>Thank you. Therefore I understand the I don't need to change my code of creating this cursor, in order to make the file name unique.
>>>>
>>>>>VFP may not create a physcal dbf at all but when it does, it's in VFP temporary folder with some temp name which suppose to be unique
>>>>>
>>>>>>
>>>>>>If I am creating a temporary cursor as follows:
>>>>>>
>>>>>>
>>>>>>CREATE CURSOR CUR_TBLNAME (.. list of columns in the cursor )
>>>>>>
>>>>>>
>>>>>>does VFP create this cursor in a TEMP folder as a random name (physical dbf file) or it always going to be the same name?
>>>>>>
>>>>>>The reason I am asking is one customer a few days ago ran into a problem where when creating an index tag for this temp cursor they were getting the message that the .cdx file already existed. Non other customers ever got this problem. I am thinking that it could be because of a glitch with the customer that had a problem. Or maybe I am not creating the cursor with a truly random .dbf file name.
