>Hi
>
>Recently I was hired to write a prototype CRM package for a Credit Union in the United States. They wanted me to prototype it in VFP because it could be done quickly and used to demonstrate the planned features of the ASP.Net version.
>
>The Credit Union is a Dot.net shop and has had experience with the length of time it takes to develop application in that environment. So to reduce the risk they had me develop the prototype in VFP. It included escalation capabilities, work flow management and host integration with Credit Union's service provider etc. The project took three weeks and two revisions before I had exactly what they wanted.
>
>Now it has been given to the ASP.net team to replicate in Dot.Net. The prototype gives the ASP.net team an interface and feature set that they need to duplicate reducing the time it will take them to create the application.
>
>That is the first time I got paid to write an application that will never be used in real life.
>
>Simon

Some of my applications were never used in real life, but it wasn't planned <g>.

Interesting concept, that prototyping. That raises some interesting questions, for example: why would the prototyping take much longer in .NET? What do they expect from .NET, in the final product, that they can't get in VFP?