I think it's a mistake to go all prg or all visual. I can't image designing a form in a prg. It would be a nightmare. Additionally, there are some classes that can only be defined in a prg, such as the session class. IMO, you're better off using a vcx for anything visual and session class for business and data classes that don't have any UI. For anything else, you need to determine the tradeoffs on a case-by-case basis.

>Cetin,
>
>First off, THANKS TO EVERYONE who has replied! =)
>
>The reason for this thread is that our team is trying to find "common ground" - we intend to come up with our own set of common base classes, and that we are evaluating what's the best way.
>
>Would it be better to have one common method of doing classes (VCX OR PRG)?
>
>Or would a mixed (VCX AND PRG) way of doing classes not be any issue? Or would it create havoc/confusion? (Like having to switch between a text editor and the visual class designer?)
>
>A VCX class can be converted to a PRG class - is it also so vice versa?
>
>
>Sincerely
>Dennis
>
>