Well said Ricardo...

For the record, I merely made a suggestion that the Fox team should consider. It was not a request. I have made lots of suggestion in the past that never saw the light of day. Que Sera Sera... For the record, the suggestion was made in the context of a discussion I had with another member of this forum. i.e., it was not directly addressed at Ken..

Quite honestly, when Ken responded to me the way he did, it got out of hand. As somebody you consider to be a valuable member of the community, I was taken aback when Ken said the very mention of my suggestion undermined the efforts of the team. I am not used to having a suggestion geting such hostile treatment...

Oh well...

< JVP >






>>Ricardo...
>
>>My only point was that while Ken is doing a good job, with respect to the >article, given when the magazine came out relative to when Ken took over, the >magazine article was already approved by MSDN. i.e., while Mr. Asherman >seemed to give credit to Ken, I merely pointed out the fact that while Ken >can lay claim to a lot of good things, the article was not one of them.
>
>I understood your point here John. I wasn't directly answering your post. It reminded me about 1 point I wanted to make to people here: Ken alone hasn't/isn't/won't market VFP. He's a big part of a team and the community is part of this team. Results are what matter and the MSDN article is results which is what counts. If there are no results then we in Microsoft and the VFP team (not Ken alone) are guilty.
>
>>Again, I think Ken is doing a great job. At the same time, I think it is a >huge mistake to not slip in a new feature or two in the service pack. I say >THE service pack because there will be one. There will be at least one issue >that needs to get addressed. Slipping in a new feature, IMO, would ensure >more upgrades. What version 8 will/will not have is not at issue. In fact, >the whole idea of getting people to upgrade to 7, so that 8 will have promise >of releasing is much akin to the carrot and stick approach. It is an approach >I would not advocate. I think loyalty begets loyalty. I think the community >deserves several of those new features sooner than later. If it gets people >to upgrade to 7, so be it. At least people are upgrading for an immediate >benefit as opposed to shoring up the economic justifications for a future >release. That is simply not a good reason to upgrade software. Compelling >features OTOH are good reasons.
>
>John, thank you for your feedback here. We will take it into consideration. You really need to see our side here to understand the dilemma. The issue here is that you are not the only one here that is asking: while you ask for your feature in a Service Pack, there are plenty of other of our good customers that need and want their features also in a SP (meaning ASAP). It's really difficult for our team to balance all these requests with really concentrating in selling VFP 7 thus highlighting the best features that 7.0 has, and getting a good, feature rich, and solid product for Toledo. We want Toledo to be be much more timely than 6.0 to 7.0 so I'm calling you and the rest of our community to wait for features that they need for Toledo. Believe me, we understand that you need them and we want to put them out there but have to do the right balanced thing here.
>
>>If we disagree, we disagree. However, I don't like my motivations or >integrity being called into question. I am simply one developer in this >community who is suggesting an approach that would help to improve the long->term prospects of the product. Nothing more and nothing less.
>
>John, I don't think anybody here at Microsoft and in the Fox group has ever called into question your motivations or integrity (this really comes from right field if you know what I mean). I personally believe that you are a great member of the VFP community and we need people like you involved.
>
>As I said in my first post, there's no controversy here John. We all have 1 common goal here: make Visual FoxPro a better product for the present and the future. I thank you for your contributions to the product and the community and am, as always, looking always forward to learning from your feedback.
>
>- Ricardo