>Throw an exception when there's an error. Returning an error code is very C/C++ like and is discouraged in .Net.
>

Craig,

I think I misunderstood what you were trying to tell me. I thought you were saying that my code should trap the error and display it, not that I should restructure the way my code is written so that I do not hav eto return error codes and messages when things go wrong.

Let me explain what I am doing and see if you can tell me how to approach it.

My code is meant to send emails out. I need to:

1. Count how many emails are sent and display this count on completion.

2. Trap any email addresses that are badly formatted and, when the process is complete, display them so they can be fixed.

3. Display any error message that occurs when sending (such as if the daily sending quota has been exceeded).

>
>>Hi,
>>
>>I'm trying to adjust a method so I can get two bits of information out of it. Previously I was just returning an error code, now I would like to return an error message along with the code. I found one way to do this is to use out parameters, so I adjusted my methods definition to this:
>>
>>

public void SendEmails(Guid emailPK, string subject, string html, out int errorCode, out string errorMessage)

>>
>>When I try calling this method like this:
>>
>>

int errorCode;
>>string errorMessage;
>>emailNotifications.SendEmails(emailPK, email.blk_subject, email.blk_html, out errorCode, out errorMessage);

>>
>>I get this error:
>>
>>"No overload for method 'SendEmails' takes 5 arguments"
>>
>>Maybe it's too early in th emorning for me but I think I'm counting correctly.
>>
>>Can anybody help enlighten me, please?