EdStauff Posted June 22 Share Posted June 22 I'm opening a file for writing using FileOpen(), which returns -1 on failure. How can I get a more detailed error code or message that would tell me why it failed? Examples: directory not found, invalid file or path name, permission denied, access conflict, etc. If there's no way to do that with FileOpen(), is there another function that provides better error reporting? Thanks! -- Ed Link to comment Share on other sites More sharing options...
ahmet Posted June 22 Share Posted June 22 When you catch error on FileOpen then try with _WinAPI_GetLastErrorMessage. If it fails show your code with _WinAPI_GetLastErrorMessage. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now