Ron,

>I sure wouldn't spend the time building what's already available, or recommend anyone else do it. Just my opinion.<

Yep. And everyone's entitled to an opinion. <g> I'm *not* saying that commercial frameworks are a bad thing and I'm *not* saying that people shouldn't buy them (gotta stay on Kevin's good side <g>) ... I'm just saying that they're not for everyone.

One of the downsides to using a commercial framework is that you're locked into that framework's methodology and "vision" of how to do things. Which isn't necessarily a bad thing, because it gets people who are just starting out to at least get started in the right direction (vs following some of the lame examples in books that get you going all in the wrong direction <g>), but it can be limiting. Plus, you often won't benefit from knowing how .NET does things because you more than likely will never have *learned* how .NET does things. Again, this isn't necessarily bad, but I think that knowing what goes on "behind the scenes" is crucial to understanding how and why things behave the way they do. And, just as *you* say .... this is just my opinion. <s>

>Thanks for your input over the last year, I've learned a lot from following your advice.<

Thanks!! =)

~~Bonnie