>>
>>Craig;
>>
>>I think most of us are aware of that anouncement, which was made June of last year my Microsoft. Also Visual Interdev and Visual J++ are "going away". However, it does not change the fact that there were "three flavors" of VB for a number of years, each one with a specific purpose but based upon VB. You might also add that VB is "going away". In Visual Studio 7.0, VB syntex, etc. will have changed from VB 6.0. It will still be a "flavor" of VB.
>>
>>Tom
>
>
>You won't be able to buy InterDev or VJ++, just as you won't be able to buy new products with VBA or VBS.

I consider that a blessing! I have been fighting the limitations of Visual Interdev for all too long. Remember version 1.0? Well, version 6.0 was an improvement but not a professional tool IMO. The technology it supported limited what a developer could do. The problem was when management such as mine insisted "all applications will be web based and written in Visual Interdev 6.0". Trying to explain VFP and West Wind connection was a better path did not work. VFP is not allowed on these premises so I welcome .NET as it should be a better path than the present one we are on.

Craig;

Somehow I feel we are not communicating. You seem to be broadcasting and restating the obvious but not addressing the point Jim and I have been discussing. I am not sure if you understand our point or you are trying to avoid it.

I agree with Jim that it is too soon to discuss anything in depth about the possibility of having “different flavors” of VFP, depending upon the required application. But the reality is that VB, VBA, and VB Script existed for years and were related to VB. By having more than one “flavor” of VFP we would thus be able to channel our development requirements based upon needs. I see nothing wrong with that concept other than it is not proven that it is feasible in this case. It is just using existing concepts that Microsoft has embraced for the VB platforms. It “could” apply to a future release of VFP as well.

I do dread the possibility of maintaining more than one version of anything. As far as VB, VBA, and VB Script go, as you go down the list, you loose functions and have to accept the limitations. That can really hurt as I have found out in a number of instances. Something native to VB as an example may not be available to VB Script. If only it were a perfect world! :)

Tom