>>>>>I don't why this is so slow. However, temp files should always be created locally!
>>>>>
>>>>>>My application has a DELETE FILE statement - it is deleting an application generated temporary file on a network drive. This works perfectly well on XP client machines but is unusably slow when issued from a W7 client PC. It can take up to 15 seconds to delete the temporary file before the user can proceed.
>>>>>>
>>>>>>The user of the W7 client can access the network drive and folder directly and delete the files with no visible delay. It is only when issuing DELETE FILE from within the application that it is taking a long time.
>>>>>>
>>>>>>Does anyone know if this is this a VFP issue or a W7 issue?
>>>>>>Thanks
>>>>>>Barry Sutton.
>>>>Tore
>>>>Even with locally created temp files there is a noticeable difference between W7 and XP clients - although admittedly not as great as when the files are on the network drive.
>>>>Barry.
>>>
>>>I haven't experienced any noticeable delay between Windows 7 and earlier Windows versions myself. But I have seen cases where VFP has not "released" files immediately, and where a very small delay has been necessary. How are the files created?
>>
>>I have previously encountered the problem you pointed out where I have had to introduce a short delay to allow the file to be deleted - but this is barely noticeable in the overall working of the app.
>>
>>This part of the app is a simple document management system based upon the creation and storage of pdfs for. When creating a pdf for viewing only the pdf file is created in a temporary folder; when storing the pdf the temporary file is then copied to the network and the temporary file deleted. It is this last step that is taking longer on W7clients compared to XPclients.
>
>It may not be an option in our case, but I have occasionally used FoxyPreviewer to create pdfs. It's free of charge, and extremely easy to use. http://foxypreviewer.codeplex.com/

Thanks for the pointer to FoxyPreviewer.