>>Sometimes I wish a programmer had just written comments on what he/she was trying to do and let me write the code! It would be simpler than debugging.
>
>Unless you are following a programmer that had no idea of what the client (user?) wanted.
>
>Hardly any success stories come from projects that failed to recognize the requirement.

My problem is more the talented but uninterested developer <g>.

But, as you say, design bugs are the most serious and expensive to remedy and in most cases its best to start over. That's the story with so many Access applications. "We had Joe work on this in the evenings and weekends. It's 90% done, but unfortunately, there's duplicate data and we get more and more errors." The biggest problem is the client's understanding that there's only 10% left to go.

Jay