Why is putting a message in the debugger better than putting it in the control itself? Seems like a lot more work to me. And I don't have to worry about the end user getting it because it won't happen to the end user. Unless the end user goes in and makes the control smaller. But then it's their own fault. :)

Thanks,

Michelle


>In that case, use an ASSERT to write a message via DEBUGOUT indicating what failed, and give the developer the option of immediately opening the debugger to see where the ASSERT triggered, indicating that your cde behaved in an unexpected fashion. This will enable the developer to deal with the error in detail when it occurs in the context that it occurs; ASSERT doesn't fire under the runtime, so you still need to make allowance for the end-user to record the error and report it back to the developer.
>
>ASSERT provides for runtime checking of program assumptions when running under the developer mode, and is ignored in the runtime. If you're putting in a safety net, protect the user from the consequences of the error, otherwise, all you get from them is "This piece of yafrax doesn't work!", with no hint of what went wrong.