And now for something completely different..... (lol)

Are you trying to sell an existing application or services to write a new application? Context is important. Secondly, if the client is concerned about 2015 (and I agree with Ken, that's not really an issue) then what makes that date magical? I mean, seriously, how many apps run for 4 years "as is" without major enhancements anyway?

If you are writing something absolutely from scratch with no existing codebase and that has to last beyond the magic year of 2015 then perhaps there's no pont in looking at VFP anyway. I'm just saying. Perhaps if it's a monolithic line-of-business app you'd be better off proposing Access (which has no end of life date at all, killing that issue). Or a basic VB .Net app using WinForms and a local SQL or XML datastore.

I guess my point, Christian, is to accurately answer your question I need a lot more context on the client, your relationship to them, and what theyt want/need.


>Once Ken Levy posted a mesage on UT regarding the life cycle of VFP and what that meant for the clients. Some client have the impression that because VFP is "dead" it would stop working suddenly after 2015, and I was looking for a good comment (preferably by MS or an employee of MS) that clears up that perception. So if you find the message or know of another statement that I could use to show to the client would be great.
>
>Christian