Hiya Mark ---

>
>I don't mean to sound critical, but I think this would be a bad approach. First, this is actually what I'd call a strategy, and strategies are best used when they can change at runtime. For static behavior that can be determined at compile-time, you just create the correct object in the first place. A "type" field (and its associated Case and If statements) is just what you want to avoid in OOP.

I gotta back up Marty a bit here. While I don't necessarily completely agree with his solution, it does adequately reflect that to support polymorphism, you have to have some branch logic somewhere.....although I would keep all that intrinsic to the object itself (and there is where I differ I guess).