Jim,

Sorry to take so long to get back to you. I just got home from DevCon after spending a couple of days in Las Vegas.

>
>That's good Craig (really)
>
>Now let's see some things for the *real* "average VFP user" - you know, those who will not (vast majority) make DEVCON or FoxTeach or ????.
>
>A damned good start would be an accessible list of Wishes Submitted, Wishes Acknowledged (but not yet 'judged'), Wishes Disregarded, Wishes Still to be *possibly* included and wishes being included in some future release (though still subject disregard if circumstances warrant) .>

The problem here is that what is rejected in one release may make it into the next. So, how do you determine what was rejected or not.

>
>Another thing would be more details of what actually got into a SP and some additional background to permit maximum exploitation. For instance, it was observed (and later acknowledged by Mr. Brown of MS) that (re)INDEX had been 'improved'. It would be nice to learn that "officially" as well as to learn under just what circumstances the improvement(s) take effect.
>[ and I must say that this may be in the SP docs - I'm awaiting my CD].

Technically, new features are not supposed to be introducted into an SP. The word given at DevCon was something like "Oh yeah, these new things were accidentally included." If there was something official about this, then it couldn't be included because it would be documented.

>
>Another thing would be an accessible list of DOCUMENTATION errors/omissions/clarifications. . .
>1) acknowledged;
>2) known;

The SP3 documentation includes a complete list of fixes

>3) being incorporated into NEXT update or product.

Microsoft has a policy og not commenting on unannounced products and releases. You'll only see things like they demoed at DevCon.

>
>These are some examples of things they *COULD* be doing.
>
>Cheers
>
>Jim N
>
>