This is sort of directed at Mike / Olaf as 2 of the most prolific contributors here, but also to all. As Olaf said " not again .." , so what is the best dotnet migration plan or more to the point WHY MIGRATE !!
I've dabbled quite a bit in dotNet, replicated most user interfaces dotNet versus VFP, used Sql Server as backend data-base where the client INSISTED. And I have yet to find a case where VFP does not hands-down provide a better development environment for the kind of one-man-show custom development that we all do. Nor have I seen on this site, or elsewhere, one single account of a succesful migration !!
But equally, I am 100% honest with my clients, tell them
1) I am a one-man-show, with the risks that entails
2) VFP will cease official Microsoft support in 2015
3) but VFP and their apps will continue to work for at least 10 years
So, with January 2015 looming large, the question is what we as a developer cummunity can/should do to
4) re-assure our clients
5) counter the inevitable anti-VFP sales-pitches
6) tell the great story that VFP is perfect for the 'cloud'
I would suggest that we form some kind of developer body with a professional brand-name, like " VFP-Insure " or some such , publish directory of members ,web-site etc etc , paid-up subscription to cover this
7) agree source code / other levels of contingency / documentation for our client projects
8) publicise this support body on all our projects
9) agree to support each other's applications in the event of dispute, illness, exit the business etc
10) this support is intended as last-resort, client pays your full per-day rates if he has to invoke.
My belief is that we need something like this, and with it, we could all continue to make a nice income from VFP for another 10 years !!
Sean M