>However, I will say that calling Microsoft is not going to solve this problem. What will happen is I will get
>a rookie, and I do not mean to offend anyone, but the fact is, he will ask me basic information and at the end
>of a long, long, and $250 incident call, I will be no further than I am now. The call might get escalated if
>I am lucky enough to get a support rep that really, REALLY cares AND has the authority and pull, but the fact
>is, in the years I have been in this business, most calls to support are fruitless. They deal with people who
>are just getting started, and it gets old. When they get an experienced developer on the phone, they treat them
>the way they treated the last 100 callers.

The gentlemen on the Fox support team all have more experience than I do, and I've been programming in Fox for 9+ years. In addition, they often post here and in other forums.

Speaking as a former member of that team, your message above is wrong in almost all particulars. The one exception being your remark about the last 100 callers -- yes, you will be treated that same way: with professionalism, respect, and a sincere desire to help you with your VFP problem.

If you don't call, your problem will not be solved. If you do call, since we've nailed it down pretty well as a bug, you probably won't be out any money, and you may not have to roll back your VFP8 version.

Seems like a no-brainer to me.

(And speaking of no brains, that's about how I feel right now. Time to go home to the family. :-) )