I thought that was an old concept (throwing one away), to be left in the past. It's true and in most cases does work, but it can be avoided with good design. There will always be changes required, users usally don't know what they want from the beginning, ideas seem to pop up into they're heads once you think you're done. But again good design can adapt to changes.

I will have to do it for one application, (my first one out of college), that went through the hands of three developers, each with his own approach to programming, all of us learning VFP while developing :).

Then again there was a thread a while back, about Extreme programming, I think it was, where the development process is in full interaction with the user, he asks, you deliver, he want's a change, you go ahead and do it, of course there's more to it than that.

I wouldn't do it, we just don't have the staff here to work like that, I bet, some clients would love it.

>Yeah, it's a difficult task to make things easy AND correct! I recently read >in InforWorld advice to consider the first version of a new application a >throw-away - and make the second version the 'real' application (assuming you >have co-operative beta-testers who understand the process).

>I have found personally that my applications improve exponentially in the >second version, and then only incrimentally after that