Hi Peter,

Allow me to add to what Ken responded.

We have hours and hours of meetings to consider every request submitted by the community. Every single request. And, yes, we do evaluate the ratings.

Sometimes we agree to a change, sometimes we don't. Sometimes we agree but modify the desired behavior or outcome.

It would be an administrative nightmare to post or email the results of a specific request. Sometimes, we get several change requests that are similar from diverse sources. Other times, we lump together requests in specific areas from, again, diverse sources.

Furthermore, what if we think an enhancement would be great -- tell the requester the same - and then find that it can't be technically done? Then we look like jerks.

We simply can't personally respond to every enhancement requests for the aforementioned reasons. OTOH, we are traditionally the most customer-driven team at MS. Feel free to email me with an issue at any time @ jkoziol@microsoft.com

Some of us on the team were Fox developers before we joined Microsoft. So we're very sensitive to your needs. Our burning goal is for you to find sucess with VFP.



>>Europa News from the Visual FoxPro Team
>>http://msdn.microsoft.com/vfoxpro/letters/
>>Get the latest updates from Ken Levy on the next version of Visual FoxPro code named Europa as well as news about Visual FoxPro DevCon 2004.
>
>Ken,
>
>I've read it all and I really like the new-features list.
>
>But two things bother me.
>
>1) You mention that the wishlist has been used. But there's no simple way for me/us to check which items have been 'honoured' and which have been 'rejected'. Personally, I contributed several items, but I see none of them back in the list you mention. That makes me wonder: were they not read or were they rejected.
>Can your team provide any feedback on the item-level to us or to Michel Fournier?
>
>2) The wishlist items can be rated by us. This gives a 'highest ratings' list. I have noticed that frequently items get the rate 'Disagree - I see no need for this'. Of course, this rating negatively influences the total score of an item, causing it to end lower in the 'highest ratings' list. I suspect that it's only one person who's frequently giving this score to any item that he/she doesn't fully understand/appreciate.
>Does your team pay attention to the ratings, or do they form an autonomous opinion about the items?