>>Have a day? Jim, what happened to interop training? How about that large group of vfp developers that don't want to do a complete rewrite??
>
>Hi Claude. I agree with your comments about this, and I agree that more needs to exist to help educate VFP developers on how to use .NET with VFP in a combined environment, just like VFP is used together with SQL Server today. I am working on some things in this area to to help VFP developers add .NET to their existing skill set rather than focusing on .NET as a replacement for VFP. It would be great to see more training on the together topic. Most companies with VFP applications I talk to are more interested in interop and slow .NET adoption adding key features like ASP.NET based web based rather than a total rewrite from scratch.

Hooray - a ray of sanity has shone it's way into the "they're trying to kill my beloved VFP with .NET" schmozzle!

I hope that there are a lot of people who, like me, have a chuckle reading these types of threads. There sure is a lot of paranoia in the VFP world.

If MS decides today that VFP9 is the last version of the product then I won't be rushing out to convert my VFP apps to .NET. I won't throw my VFP disks into the bin and wail inconsolably about the death of "my baby".

I'll continue developing with VFP for a few years, learning about .NET (and especially VFP/.NET interop) and see where the winds are blowing regarding development for the Windows platform.

Maybe it's my relaxed Aussie upbringing.