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...



>>In addition to speed in development and runtime there is also the issue of later modifications. Let's say there are two developers and one prefers to code classes in prgs and the other to code them visually. If later one of them leaves the company which method allows for the most easily done modifications in the future? I know some developers that prefer to put their classes in prgs and others that prefer to do everything visually. I think that generally a new programmer coming on board would be more successful immediately having to modify classes designed visually. That has only been my experience though. Which method most benefits the company and the customers in the longrun?
>
>I've worked in several places where the code was distributed in all sorts of ways - the only thing I never had was code in a dbc. I've had code in scxes, vcxes, prgs and memo fields (i.e. scripts). No problem with any of this per se, and I think any programmer who finds that any of these just stink is the problem himself.
>
>Regardless of where the code is, what matters more to me is the clarity. Refer to Craig's tagline about the maniac who knows where you live.