How can I get a reason of error when calling DirCreate function

[SeunghunBaek]

I got a return value 0 when called DirCreate() function.

I'd like to handle the error code according to error case.

but I can't know what happened during the function call.

could anyone please help me to catch the error case?

is there GetLastError() function like MFC?

[BrewManNH]

DirCreate only returns 1 or 0 depending on whether it succeeds or fails. Where are you trying to create the folder, and what OS are you using? If it's a protected location on Vista or above, such as C:Program Files you will probably need to run it under administrator's credentials.

[SeunghunBaek]

i'm using Autoit on Windows 7.

What i want to know is about specific error case when errors occurred.

i think there would be many error case.

for example due to lack of disk space, wrong path, already existing directory...

but i only know whether success or not in Autoit platform.

i really want to know how to get a specific error code like win32 api or MFC.

please help me.

[JohnOne]

The API only sets 2 errors

ERROR_ALREADY_EXISTS

ERROR_PATH_NOT_FOUND

Simply check those two things.

FileExists()

"due to lack of disk space" I don't think so, I don't even think a folder takes any space, it has no byte value, so if you don't have enough space to create a folder you have bigger problems than those you think you have.

You can even test for the disk space if you really believe that to be an issue.

Edited January 22, 2013 by JohnOne

[BrewManNH]

Well, if the folder already exists, then you should be checking for this before trying to create it. (FileExists works on folders too). Also, if the path is bad, you should be checking for that before trying to create a folder in invalid paths. After that, it is usually permissions issues on Windows 7. There is a whole slew of WinAPI functions in the help file, I don't use them much myself, but there might be one in there that could work for you. Unfortunately, natively, DirCreate doesn't tell you why it didn't work, just that it didn't, validity tests are your (the coder's) responsibility.