I have addressed the following proposed solution to all who have responded in this thread (Bill, there is a note for you at the end):

I would like to see a Kill Thread feature for the UT. When responding to garabage threads like this, users will have the option to check a Kill Thread CheckBox. Before midnight, a process would fire which would determine if the majority of users (who responded) voted to have the thread killed. If so, the thread is dead - killed forever.

I feel so strongly about this that I am willing to provide 100% of the financing for the implimentation of this feature. If you are listening Michael, please email a brief proposal and your phone number. You may want to limit this feature to paying members - a good incentive.

As for you Bill,

IMHO, many of those who responded to you were far too diplomatic.

For those of us who make a living providing VFP solutions, these rumors affect our careers. In the last year, every IT manager I have met with has heard these rumors and, as a direct result, I have lost thousands of dollars in jobs and contracts that I would otherwise have acquired.

Whatever motive (e.g. entertainment, malicious, etc.) you have in instantiating this thread, you are messing with my career and my earnings of which my family depends. This is personal, not business.



>Well folks, I hate to fan the "FoxPro is dead" thread, but nevertheless, I'm reporting what I've been told. Note that in the following, I'm not saying Fox is dead but trying to provide some insight to what VFP is thought of within the sales and consulting arms of MSFT.
>
>I have a computer consultant friend of mine who I've known for roughly six years or so. He used to be a FoxPro developer and knew it rather well. We talk about once a week -- I consider him a reliable source. Recently (perhaps today?) he went on a second interview with Microsoft Consulting (I won't say where to protect the guilty). He's a pretty intelligent guy and has good experience with a broad selection of products -- I think he'd be an excellent hire for MSFT Consulting.
>
>He spoke to a recruiter regarding a final interview. The recruiter is someone within MSFT Consulting. The recruiter went over his experience -- VB, VC++, Access, Delphi, SQL Server, Oracle, Sybase and others, and asked pertinent questions.
>
>The recruiter asked if he had any other experience. He mentioned his FoxPro and VFP experience on his resume. The recruiter told him specifically "Don't mention it in your interview." I repeat -- the recruiter told him specifically "Don't mention it in your interview."
>
>The implication was obvious to both -- if you want a job within the arm of MSFT Consulting, don't mention VFP. It's not used and is actively discouraged.
>
>Other things mentioned -- he has a friend who joined MSFT Consulting -- a person whom he worked with at his current job, has told him that it is common knowledge within MSFT Consulting that VFP will not be in the next major release of Visual Studio.
>
>He also "reported" that it is also common knowledge that MSFT is not actively working on any sort of major release of VFP. Now I know that's not true but I'm just telling you what's going around the water coolers at MSFT sales offices and MSFT Consulting.