>
Well, glad to see your knickers aren't in a 'bunch' over this. <g> Hope you understand that this was, well, just too juicy to pass on. *bg* I fully expect you'll return the favor some day to keep me on the straight & narrow as well....
>

In the grand scheme of things, it is an insignificant issue. No need to get upset over something like this.

For folks listening in, is your day to day life any different since the website was changed? Further, once you found out about the state of the website, did your life change other than being PO'd that MS did not mention VFP?

My guess is the answer to both is No and No. Folks continue to get in an uproar anytime VFP is not mentioned. FWIW, I don't think the solution provider site has ever been corrected. Although, I may be wrong here.

Ultimately, the fortunes of VFP have been determined. A mention or lack of mention on a website is not going to make a difference.

In this case, I am sure somebody decided that instead of getting pestering and whiney e-mails, they would change the site...


>
I think, underneath all the bluster, we see pretty much eye to eye, in that folks should use the best tool for the job. I think that rather than pick others apart because they may not actually know they have alternatives we should do our best to educate (not harrangue <g>) them.
>

I think I have tried to educate. However, there are those that have a chip on their shoulder the size of Gibraltar (spelling...). Mention VB and you have been dis-loyal to VFP. Again, I am not my dev-tool.

The right tool for the job? There lies the hypocracy. Folks will tell you they use the right tool for the job. Of course, the right tool somehow is always the same. Objective analysis? I think not..

Me harrangue? I don't think so...


>Personally, I see a great deal of benefit to ADO and I'd really like VFP to have it but since we can get to it, why bother?
>

I don't understand this statement...