>I think, as Mike mentioned, this is a minor issue. It's the minor issues where we are more likely to let programmers make their own - often differing - choices. Now if you work with an "intermediate VFP programmer", like I did recently, who doesn't know what data normalization is, programs by copying and pasting the same code everywhere, and has other really poor habits, then you can tend to say with more certainty (great certainty) that the programming is wrong.

Huh, sounds like trouble on a long run. In menu cases hiring such person
cost you way more then what they are actually paid. I don't believe
in myriad of programming 'philosophies' at the same spot. As much as I did
not like constrains when I was young developer working for someone else,
I tend to understand now other side of a coin. Having strictly folowed framework or at least unified/respected coding patterns is of great Importance. If I ever open software shop on my own, I wld not seek for young VFP 'experts', but simply look for a young people with just a bit of common sense / correct attitude. [Girls preferably, they are much more tidy! :) ]
I use my own framework for years (4th gen) and realised that I actually stopped 'programming' in a classic way long time ago. What I do, is develop database and then routinely implement common functionality patterns & reporting in a very uniform way. It really pays back.

>
>How's the weather in Cyprus? Our missionary friend just moved from there to his wife's home country, Switzerland.
>

Sunny as always. We appreciate winter/rain here.
And guests at any time :)