Hi Bob,

I understand your frustration and I'm not sure if would as restrained as you are in this situation but I thing you took Garrett's messages in the wrong way. He was trying to help you to resolve the problem not to offend you. His comment about "vengefull customer" wasn't directed at you at all. I agree with him, that now that you have solid repro code, you should contact MS PSS so they can help you. They may even provide you with hotfix if there's no other workaround. I doubt that you would be charged for that support call. It seems to me much better alternative than move code back to VFP6.
UT is just a message board where VFP developers help each other. MS VFP team members monitor it and they usually responde to posts if they have anything to say. I bet they would use your repro code to nail down that bug. However if there is no workaround exists they couldn't help you. Anyway, it'll take a time for them to work on this bug.

Just my $.02 :


>I spoke too fast for my own good regarding the "marketing". I forgot to give you the details. Earlier today someone posted about their success with a VFP8 migration (we deployed ours two weeks ago and thought it was successful). BTW, like this poster, we went about a week without any issues, and then BOOM! I was getting ready to send Ken an email like this one thanking everyone and renewing my UTI membership for a year...VFP8 rocks!:). I still would if I could get a response from Microsoft. VF8 rocks, it's just not ready for primetime as implied! If I am wrong and it's my app, my bad, but I don't "thank so"! I think my code proves that, why I need to call Microsoft and spend two days wading through there "queues" is beyond me! Have a slice of this...it got a response!
>
>Thread: 815910 Message 815910
>I just wanted to say thank you to everyone who has answered questions over that last couple weeks for me. We managed to migrate our VFP7 application to VFP8 and deployed it to 7 customer sites on Monday. ...."
>
>
>Ken Levy responded today in Message 815954
>"Thanks for posting this. I will forward it to the entire VFP team at Microsoft ."
>
>Now don't get me wrong, I am all about this. I want VFP8 to succeed. However, I also cannot understand why on this thread success warrants a response but all I get is doubts, even after posting what I feel is a significant problem. I spend an entire day walking backward through code to reduce the problem down to base classes so everyone could see it! Are these problems not as important as the successes? If that is the case, what is this board for? The people we need buying into VFP are not here...we are already sold!
>
>Listen, if the VFP community is to survive, we cannot walk away from problems or assume that it is the developer and tell them to call tech support as Garret suggested. Moreover, we should engage in banter that divides and seeks to mince words or be rhetorical which is basically what I got...I had prove and then prove, yet, the problem is still there. Yes, Microsoft will solve this problem, but how many VFP developers will we lose in the process? Are we replacing VFP developers faster then we are gaining them? I think not!
>
>Try this one on!
>
>>But if i remember correctly there was no SP1 planned for VFP 8,its directly to VFP 9.
>
>You do not remember correctly. :) Nobody from Microsoft ever said there would not be an SP1. That was rumor in the community by people who did not read my message very well. What I posted (which is still here on the UT) is below:
>>But if i remember correctly there was no SP1 planned for VFP 8,its directly to VFP 9.
>
>I know I'm dust for posting this message, but this whole episode and the resultant response here on UTI has me questioning VFP for the future. Real tragedy, because VFP8 rocks and has so much potential...the powerbuilder for SQL Server 2000 and beyond. However, ignoring developers problems et al is very dissappointed to say the least. All that was needed was a legitimate response. If you feel that I received that, I smoked once again, but I sincerely believe that ignoring my post is a "root cause"!
>
>Thanks for listening,
>Bob

--sb--