Thank you for your reply, Shahram--
The problem is that I'm kind of pressed for time and I had gotten deep into the first method of creating server controls from *scratch* and implementing the event handling manually. While I can accept your opinion that this is "not" the recommended approach, it would have helped to explain to the reader everything that they would need to know to go this route.
Moreover, your example custom control was very OVERLY SIMPLISTIC...I was developing a control with multiple <input> html buttons that would have to raise postback events and handle these events accordingly. In your simple example control, you have a single button which has its 'name' attribute set to the UniqueID of the control itself, which I'm sure left several readers in the dark when they had multiple buttons within their control.
What you should have done is have the reader set the <input 'type'> attribute to button and add the 'onclick' attribute, passing the 'Page.ClientScript.GetPostBackEventReference' method passing the control's reference to itself and an identifier for the button or object that caused it to the 'RaisePostBackEvent' method. This would allow the control to identify exactly which control raised the postback event.
I ended up having to go to http://www.code-magazine.com/Article...ickid=0511051"
which explained this the right way.
You honestly caused me hours of confusion when you totally abandoned the reader by not even FULLY explaining the proper way to create controls manually with their own event handling..specifically with your overly-simplistic credit card entry control with a single button..