David,

That's an interesting suggestion. However, there are some risks and complexities involved. Let me quote from http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone

Problem Resolution Services
Microsoft Problem Resolution Services provide assistance for problems with specific symptoms encountered while using a Microsoft product, where there is a reasonable expectation that the problem is caused by the Microsoft product..

Problem Resolution Services are delivered on an incident basis. A Problem Resolution incident is defined as a single support issue and the reasonable effort needed to resolve it. A single support issue is a problem that cannot be broken down into subordinate issues. If a problem consists of subordinate issues, each shall be considered a separate incident. If a problem is determined by Microsoft to be the result of a defect in a Microsoft product, the customer will not be charged for that incident.

Incident Submission - Getting Started To open a Software Assurance (SA) problem resolution request, you must provide the following information:
Software Assurance Access ID*
Server product edition and version that shows the issue
Authorized Contact information
* The Software Assurance access ID is provided to authorized individuals by a company’s SA Support Benefits Administrator. For more information, contact your Microsoft sales representative.

The developer must first agree to the installation of software that will collect technical info about the machine. Only 2 incidents will be handled for free. (I find many more bugs and doc-flaws in the product version's lifecycle.) One must start an incident with a commitment to pay ($99!) and it is MS who will decide whether or not the incident is the result of a defect.

This is not really an inviting environment for the developer who is 100% sure that it's a bug or documentation flaw. MS should introduce an alternative path for those submissions. OR, they should be more active HERE!


>Peter,
>
>How about use up one of your VFP support incidents and get in the official loop for some action on your problem? Most people who own VFP have NEVER used any of their free support incidents, according to those who work in the support department. They encourage VFP owners to take advantage of the support team's many years of expertise and their connections directly to the dev team.
>
>I notice now and then a blog entry from lead developer Calvin Hsia where he shows something he researched because of a customer request or support call, so using a free incident might be the best way to get your problem escalated to the right person without just having to make a post and hope for the best.
>
>Caveat: I don't know what the support programs are outside the US, but I assume there must be some free support incidents available to any VFP owner. I could be wrong...
>
>>

IF you have a question
>>  IF you have tried the community first
>>    IF it is about a presumed bug or lack of documentation
>>      IF you suspect that it can only be answered by a member of the vfp devteam
>>        IF you are not an mvp
>>          What do YOU do?
>>        ENDIF
>>      ENDIF
>>    ENDIF
>>  ENDIF
>>ENDIF