CopyFile()

[magic]

I am using CopyFile, but want to know how I can confirm the copy has been sucessful, does it have a return type, or is there another way to find out if the copy has sucessfully taken place?



Magic

[bennyandthejets]

Have you tried googling this question, or searching at MSDN? We don't have time to answer these sorts of stupid questions. The return type of a Win32 API function is not in the scope of this forum.

[swoopy]

I hope I don't get flamed for answering this.

If function succeeds, return value is nonzero. If function fails, return value is zero.
To get extended error information, call GetLastError.

[bennyandthejets]

FLAME FLAME FLAME

Just kidding. I don't mind people answering magic's post, I just wanted to tell him/her the proper way to use these forums.

[swoopy]

You made a good point. This was one I just happened to have the answer at hand.

[JasonD]

Originally posted by magic
I am using CopyFile, but want to know how I can confirm the copy has been sucessful, does it have a return type, or is there another way to find out if the copy has sucessfully taken place?

I'll give you a tip: search on Google for "MSDN functionname". For example, in your case: http://www.google.com/search?q=msdn+CopyFile. It almost always returns what you want in the first or second result. Google is way better than MSDN's search feature.

Also, bennyandthejets is right. No one has the time to answer these sorts of questions, when the answer is freely and easily available from MSDN. If you are having trouble understanding how to use this information, that is when you should ask a question here.

[magic]

Thanx for the help - i'll try not to bore you with my inferior petty problems again.

Magic

[Cat]

You are free to ask questions, but most people here feel that we're not your personal reference manuals. And asking better questions is in your best interest, as well -- you spent 8 hours waiting for an answer that Google would have given you in 8 seconds.

Posting questions like how to achieve some task, how to use some command that is poorly documented, which of several options for a task is best, etc. are good questions -- they aren't trivially simple to find answers for on your own. Asking about the parameters or return of a function, though, is something best suited for Google.