Hiya Jess!

I read the article.

>
>LAN Times review on VFP 6.0
>1. "VFP 6.0 is sluggish still; RDBMS connection could be simpler."
>

Yes, sluggish IS slow. VFP6 is much faster than in was in bringing up forms. MS claims 10x faster but haven't tested it and rather doubt that claim. I have no idea what they are referring to with "simpler RDBMS". It's the same with 6 as 5.

>
>2. "The nature of the programming language is still procedural, but the new version has improved object capabilities and includes a library of objects, such as navigation buttons and other Windows controls, that you can drag and drop in your application."
>
>I just want to emphasize with the term "PROCEDURAL". As far as I know, VFP supports procedural still but not promoting procedural programming because the nature of the language is already full object-oriented programming.
>

You are correct. New Assign and Access methods make it even more possible to get outta procedural constructs.

>3. "New applications-development projects should take advantage of contemporary programming tools, so we won't try to persuade you to adopt the dated Visual FoxPro as your main programming language. But if you have existing FoxPro investments or fluent FoxPro developers on staff, mark your calendar for the release later this summer and begin pushing those old programs toward the new century."
>
>This claim is ridiculous, it scares new comers because it does not promote VFP as a good choice for new projects but only to existing FOXPRO investments and only current FOXPRO community.
>

It's an attitude to be expected. We know better. At least we're now getting some grudging respect...my opinion is that we're a helluva lot better off now than we were 1 year ago and we'll be even better off 1 year from now. Much to my surprise things are going exactly as they should to get VFP recognized as an acceptable Win development tool. Don't expect major paradigm shifts overnight but, just maybe, we'll be attracting a lot of new developers into our ranks soon.