Mike,

>I understand. However, whats more visual, I giant case statement with numbers, or a list of methods and events that can be viewed from a class browser like utility or intellisense?
>

I told you it was a poor example! OK, in this case, I might only need to add a few lines of code to a couple of events to call form methods and I am done. Whoops, a modem, eh? Gotta put something in to test the CD line. The rest of the CASE gets axed or just ignored. I don't have to fire up another window (class browser, help file, etc.) to get to the meat. Sorry, no Intellisense yet. VFP6.

>What happens if the template needs changing? How many case statements will need updating?

I'll cross that bridge when MS updates the control :>)

>>Call me lazy.
>
>A Lazy Developer. Somehow, I don't think you're the first :-P

Thanks. :>)

>When you think about it, doing the dirty work early on, lets you be lazier when the time comes to both use and update your class :-)

I agree. I was just trying to see if I could shed some light on the original poster's question. I thought I had a decent example of where it might be useful. I'll go back to work now...