>>>The result is the same in Silicon Valley. Our company even had speakers from Microsoft come to tell us all about .NET. VFP is not an option and is not promoted by Microsoft. Corporations listen to Microsoft and the word is go .NET. How can you go wrong by following the advice of Microsoft? Where does Microsoft spend its money? On promoting VFP or .NET? It can all be so much fun. :)
>>
>>In suggestion from Venelina's, anyone would be interested if UT would launch a survey for knowing how much VFP developers would be in favor or making VFP 9.0 to be VFP.NET instead? That would include keeping the product as is, more powerful, more flexibilities but with a full recognition into the .NET framework.
>
>
>Michel,
>
>That's a great idea! But why wait for VFP 9.0? And let's also add a proviso that whenever it happens, it be VFP.x, where .x is whatever MS is calling the premier developer toolset it promotes, supports, and sells. Also understand that the appelation VFP.NET means nothing as far as VFP itself is concerned. We need not assume that VFP.NET in any way implies a redesign around the CLR. This is purely an act of marketing, and an expression of sincere commitment to a reasonably large number of long-time Microsoft customers. MS has assured the VFP community it is not planning to crush VFP or force us to switch to .NET unless and until we're persuaded that this is the best course to take, right? What would it cost to change the name from VFP to VFP.NET? I strongly believe that the benefits to Microsoft of such a change would be well worth the cost.

A genuine stroke of genius, Mike, and one that Microsoft is fully experienced with. They announced their .NET servers for instance, shortly after .NET was announced. The unofficial spokesmen for MS here on UT repeated often that .NET was here because their servers were available. Over a year later MS admitted that it had over-hyped that issue and that the servers were (now) coming soon.
Just as we know that being in the VS box provided great comfort to many decision makers who were otherwise convinced by the 'VFP is dying' rumours, so being VFP.NET can provide the same comfort.
Surely the boxes for VFP8 are still at the design stage, so there is time for VFP.NET to be delivered early in the new year.
Best - it can only help the efforts to market .NET.

FANTASTIC!!!

>
>Mike