Well, Craig, we generally are smart enough to recognize that dates can, and *do*, change!

The requirement for an implementation date (in this discussion) is for the sense of committment - you say it will be in the next release, presently due to ship 3rd quarter (though ship date may change) does the trick - it's STILL *IN* the next release.

I see I need to bring my lawyer when you read my stuff.

Cheers,

Jim N

>>David,
>>
>>We'll have VFP for the next 5 years even if MS stops producing VFP tomorrow.
>>
>>We've been buying VFP and VS in droves already and it hasn't gotten us very far, has it? I don't know how a subtle 'message' like that would get through when a whack with a 2x4 hasn't done the job!
>>
>>Your list of what YOU want ain't bad, but it's only a start. What we really need is some DIALOGUE between MS' VFP team and the Developers User Community, and THIS forum seems an ideal place to me!
>>
>>Dialogue which has us agreeing on future enhancement requirements, then MS team responding in some fashion, then us arguing some more, then them answering again, then us specifying a 'final' list, then them responding with planned IMPLEMENTATION DATES, then them reporting progress every 3-4 months and US pushing when something seems to be slipping.
>
>
>You'll never get implementation dates. VFP is forever tied to Visual Studio and will have to wait for dates based on when the other Visual Studio components are ready. For example, Visual Studio 6.0 was originally slated for release in May 98. Current date is September. VFP 6.0 is not the reason this date slipped, VB and VI have had some major problems.