I got this vbscript:
Set FSO = CreateObject("Scripting.Fi
' my objective the windows temp folder
Set objFsoFolder = FSO.GetFolder("C:\Windows\
Set objFsoWindowsTemp = objFsoFolder.SubFolders 'collection of subfolders I don't use
On Error Resume Next
For Each file In objFsoFolder.files
wscript.echo file
' IF FILE NOT locked THEN
FSO.DeleteFile(file)
END IF
Next
msgbox("Done deleting batch files")
Set FSO = nothing
Set objFsoFolder = nothing
Set objFsoWindowsTemp = Nothing
I want to get rid of the On Error Resume next line and test the status of the file if it is locked before removing it.
How can i test for a file lock?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Just keep the "On Error Resume Next" statement in your script, but add the following 4 lines below the FSO.DeleteFile method.
On Error Resume Next
For Each file In objFsoFolder.files
wscript.echo file
FSO.DeleteFile(file)
If Err Then '<-- ADD THE FOLLOWING LINES
wscript.echo "Unable to delete file '" & file & "'. The file is currently locked by another process."
Err.Clear
End If
Next
You cannot delete a locked file you will get an error like
C:\WINDOWS\Temp\QUERY.LOG
C:\WINDOWS\batch\delete-te
Tested the script from jkaios, it works but you can only log that the file cannot be deleted for some reason.
Got now:
Set FSO = CreateObject("Scripting.Fi
' our objective the windows temp folder
Set objFsoFolder = FSO.GetFolder("C:\Windows\
Set objFsoWindowsTemp = objFsoFolder.SubFolders 'collection of subfolders
On Error Resume Next
For Each file In objFsoFolder.files
strResult = strResult & file.name
FSO.DeleteFile(file)
If Err Then
strResult = strResult & VBTab & "Unable to delete file!"
Err.Clear
Else
strResult = strResult & VBTab & "File deleted"
End If
wscript.echo strResult
' reset strResult to an emtpy string
strResult = ""
Next
msgbox("Done deleting files in C:\Windows\Temp")
Set FSO = nothing
Set objFsoFolder = nothing
Set objFsoWindowsTemp = Nothing
Will wait for some guru who can tell me how I can test a file if it is locked by another file or not.
>>it works but you can only log that the file cannot be deleted for some reason
What do you want to happen? What does ignoring an error because you are unable to delete the file versus checking if it is locked and then not even trying to delete it?
There is nothing in FSO that provides checking if a file is locked that I am aware of, and FSO is the only mechanism by which you can access the file system, barring rolling your own COM object. You can test for a locked file via the Windows API, but the API is not accessible to you from VBScript unless you, again, roll your own component.
Business Accounts
Answer for Membership
by: AzraSoundPosted on 2006-10-23 at 12:36:33ID: 17791033
If the file is locked does it actually let you delete it? Also, by locked do you mean exclusively opened by another user/process? I wouldn't imagine it let you delete it otherwise.