File object will not delete directory unzipped by Zip Object

[SuperDisk]

Hi there. I am downloading zipfile from server using FTP, unzipping it into a folder using Zip Object (Clickteam), then trying to delete it using the file object.

However, the file object doesn't want to delete the directory.

When I inspect the unzipped folder with Explorer, its 'Read only' property is set.

Why does the Zip Object set the unzipped directory to Read only? Is there any way to delete the directory without having to do it with Explorer?

Should I use a different Zip Object than Clickteam's?

Thanks.

[SuperDisk]

Well, my little hack solution for now is to create a batch file with the text:

rd /q /s directory

and then run it instead of deleting using the file object. Quite lame. Is there any elegant fix for this?

[Gustav]

If you didn't tryed yet: Read the error code from file object with LastError( "File" ) after you wanted to delete the file.
Then have a look in the MMF help file to know the meaning of the code. This could help to solve the problem, if you know what's happening.

[SuperDisk]

I tried. The error was just an empty string.

[danworth]

If you're referring to the "read-only" attribute set in the general tab you can ignore that. Most folders have that set in windows. The ACL is what matters.

Where are you unzipping the file to? If you are using Vista/7 programs are likely to be denied access to the program files folder. Its recommended that you store your temp files in the temp folder ie: "%temp%\myappfolderhere" You shouldn't have an issue removing the files from there. If the files are going to be reused you can store in "%appdata\myappfolderhere"

[Danny]

I also had this issue, I ultimately used the File-Folder object which deletes folders and subfolders with 0 issues.

[Gustav]

I ran into such a strange issue some time ago, that the File object didn't work anymore.
Well... a file action failed and an error code was set. The File object only works again in further actions, if you reset the error code.
In some cases you think there is a bug, but if you know that you only have to reset the error code it works again...
Good to know. ^^