>>I have four new apps starting over the next 30 days. I will do 2 in VFP7 and 1 for sure in C#. The other - I'm still debating on. If I were starting them six or 8 months ago - they would have been in VFP. If I were starting them in 6 or 8 months from now. they would probably ALL be in .NET/C#. My point is - that I don't see us in VFP for a whole lot longer (12 motnhs?) other than legacy support. With that, I'm having a hard time seeing us upgrading to Toledo - and I/we have been die-hard VFP supporters for a long time.
>
>It is obviously your call to us what developer tools you use. Toledo is going to be an exciting version of VFP. If you get MSDN Subscriptions, you get VFP, VS6, VS .NET, Windows versions, etc. and you get new versions of VS .NET and VFP right when they are released (before anyone else).
Yes - we have MSDN subs inlcuding a universal - love 'em - though I must say that I DETEST having to register them to individuals as opposed to just the company.
I wish I had a crystal ball to see where VFP will be in 2,3,5 years. Just being "still here" is not enough - COBOL is "still here" :-)
Ken B. Matson
GCom2 Solutions