>I agree. However, a developer does not always have the freedom to design as he/she pleases. Most often a standard is already in place and the programmer has to adhere to those standards whether they agree with them or not. Especially where teams are concerned or the IT Manager is not a developer (a scenario I have run into numerous times). I wonder how many VFP developers would answer honestly if asked during a job interview "Do you prefer to work with classes in a vcx or in a prg?" and "Are you able to work with classes designed either way?" not that the questions are ever asked...

And the answer I'd like to hear from a candidate would be "I don't care - both are OK for me". Specially with the advent of the Document View window, either is easily navigated.

And in-house standards need to be respected. A good team member may need to be some sort of chameleon in that, to follow the common programming style, so whoever comes to maintain the code doesn't have to change his glasses to read a different coding style.

Of course, if the existing style is rife of bad programming practices, then... good luck to both the team and the new member. They'll need it.