>>
>>You're right... and I'm going to say the same thing here again. Microsoft typically markets new releases. Once the release has been out for awhile, you don't see much about it. VFP7 is NOT RELEASED. I don't expect to see anything for it yet.
>
>Craig,
>
>If we're going to judge by what Microsoft typically does, then wouldn't it be safe to assume that MS will never give VFP a fair shot? Some serious damage control should have begun the moment that MS announced VFP's removal from VS. We're being crucified in the job market, and you're content to let MS stall us another few months? Is that the RTM date, or the next DevCon date, or maybe we should wait until VFP 8.0, since the main highlight of 7.0 is its removal from the box. Meanwhile we've been inundated with BS about .NET for a year before it even exists! Don't expect to see anything if you're not willing to simply ask for it.
>
>For the benefit of lurkers: please vote! Add your name to the 776 (and counting) supporters on the list at http://www.ideaxchg.com/ix07/bymda/mdav0016.htm
>
>Mike

.Net is NOT a product... it is mostly marketing. When you dig into it, there isn't lots of new technology there. Much of what you see in VS.Net was originally called COM+ 2.0, but that wasn't sexy enough for marketing. I will also remind you that VFP7 has had feature blurbs on the MS site for several months now.

As for the list, it's a waste of time. MS already knows our concerns and the marketing budget has already been set. IMO, we will be better off supporting the marketing efforts that have been made to this point than screaming about things that we have no control over and won't be happy with when they do happen. My point is what I've said before... it won't matter what MS does... there will still be people that won't be happy with the marketing effort. VFP will NEVER get the marketing dollars of VB, but some people are wanting just that. It's time to wake up, grow up and face reality.