>Yes you're right, fox code can be called from .net and visa-vera. My concern isnt so much of a technical nature as it is a practical one. What it boils down to is the simple fact that since there is no VFP .NET how the heck are you supposed to convince CLIENTS (you know, the people that pay my bills and stuff) to use it? I can jump up and down and point to 100 web pages that say 'yeah, its the right tool for the job' but there is no hiding the fact that compared to VB programmers our numbers are small. Clients worry about the 'run over by a truck' syndrom (lost developer) and what are the odds of finding a local VFP guy as opposed to a local .NET guy? What about 3rd party tools and gizmo's and stuff? There are already more .NET toys than there are VFP toys and heck it just came out! It's a compatibility issue. Sooner or later I'm gonna be standing in front of my clients feeling like a clown trying to tell them to use VFP when everyone else in the world is saying otherwise.

You have to work that out for yourself obviously. THere's a good case to be made for VFP esepcially for shrink wrap and applications that go to the desktop. There's also a case to be made for productivity which is vastly better than in .Net.

As a developer you have to think about whether you want to be developing in VFP and take the risk of 'falling behind' in the curve. I think the best policy for the moment is likely to keep working with VFP but also learn .Net and compare - using the best tool for the job.

There may come a time when .Net is the better tool for the job both technically and logically...