We have the same direction as far as technology, language and timeframe are concerned. I just can't predict if at the time Toledo is released, we already converted our apps significantly. If not, we might be using it (Toledo) to maintain legacy apps or, use VFP7 until all our .NET apps are ready certainly because .NET and J2EE are the future of computing.

>>There is a significant percentage of existing VFP developers who have not yet upgraded to VFP 7.0, so this is the primary target. There will be more more marketing of Toledo when it is released than existed for VFP 7.0 when it was released. But until then, getting people who have not yet upgraded to VFP 7.0 (either via upgrade or by obtaining MSDN subscriptions) is a key marketing effort of VFP by Microsoft. There are other things outside of the FoxPro community always in the works, some have results like getting VFP 7.0 mentioned in a recent XML Magazine article about XML databases vs. relational databases, etc. Microsoft is very committed to marketing VFP now and after Toledo is released,a nd Microsoft cares about the sales/revenue of VFP both stand-alone/upgrade as well as being obtained via MSDN subscriptions. Until Toledo is released, sustaining VFP 7.0 upgrades is a key effort.
>
>PMFJI - but do you anticipate that Toledo upgrade numbers will be any better than current VFP7 upgrades? I love VFP and I love VFP7 - but we, for one, are in transition to .NET. It is simply where the future is.
>
>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.
>
>Thanks for your efforts,