>In my opinion, the risk for bugs is much higher for PRGs than VCXs. And the speed of development much lower. But, I guess that those who are very fast typists and who also like to do it prefer to define classes in PRGs. I'm not that kind. :)
>
>Vlad
>
>>It's strictly a matter of style and design, Vlad. Neither one is inherently better than the other. They both have their strong points and weak ones, as well.
>>
>>George

Funny, I kinda feel the opposite. VCXs are much easier to deal with in the maintenance end than PRGs. Just open the class and go right to the method, rather than have to search for it. On the other hand, I like being able to define something as either a procedure (code that performs an action) or function (code that returns a value). I've never worried to much about the additional time it takes to type out the procedure/function declaration. If I have to take that into account when trying to figure out how much longer it's going to take in development, then I'm probably in the wrong line of work;-). As for being more prone to errors, it's hard to quantify something like that, so I think that the point is subject to debate.

George