>>>Rather than add fuel to the VFP & .Net fire, shouldn't Microsoft shift VFP to replace Access? What would the technical difficulties involve? What would be the benefits? What would be the downside?
>>
>>This will NEVER happen. Mr. Levy made it pretty clear some time ago that almost no effort will be made to give whatsoever kind of advantage of VFP over anything else.
>>
>>I'm sure that if QBasic would still be there that it would'nt be close to impossible to put good words in favor of VFP over QBasic.
>>
>>I've been arguing for a long time over the marketing of VFP. Nothing happened over that and apparently nothing ever will. Still some persons at MS say that feedback is important. They never said that they'd respond to that feedback though <vbg>
>
>Denis, M$ has no time to even consider giving VFP any major exposure... they have their hands full with the VB6 revolt going on right now!!! Check the UT front page for the juicy tidbits.....
>
>http://www.eweek.com/article2/0,1759,1774528,00.asp
>
>Tommy

Thanks for the link Tommy.

Too bad for them. supporting VB6 by means of enhancing it would mean slowing the .Net jet a little bit.

The only chance for them would be for MS to commit to respond to eventual problems mentioned about VB 6 and releasing SP if necessary. But no evolution of the language under no consideration. In the meantime they'll probably work harder to make a real converter from VB -> .Net