>SNIP
>>I've heard that NYS Depts. used FoxPro quite a bit, at least they used to. But now it seems that someone has sold them to the VB/SQL migration instead of VFP/SQL...
>
>Boy, that's a situation warranting some attention from someone!
>Do you have any idea if this includes some migration "plan" (in quotes because it must be hard to plan for something still in EARLY development by it's supplier) to .NET?
>

Hi Jim,

For that NYS project, I don't know. But if they were sold on converting to VB from Fox instead of Fox to VFP, I'm sure that convincing them that it's a stepping stone to .NET wouldn't be hard to do. Then again, all it takes is an ignorant (or clever) person to say, nope you can't do xxxx with FoxPro, but you can with VB, regardless if it's true or not. I'm sure that the availability and interchangability of VB programmers is more attractive to businesses and gov't as well.

I guess what this comes down to is, if MS VFP marketing is focusing on keeping existing customers and having them upgrade to newer versions of VFP, it's pretty blurry.


- Brian