>>>>Peter,
>>>>
>>>>>I'm sure it's not the only serious bug (for me actually a showstoppper), so I've decided to return to SP1. I'm not sure yet what steps this will involve, however.
>>>>>
>>>>>Also I have decided I'll not gonna send them a bug report now. First they better give proof that they still appreciate the contact with the community, for example by giving regular presence here.
>>>>
>>>>I have entered more than a handful of bugs between SP1 and now and MS did follow through on most of them. Posting to the MS bug site takes about the same time as to discuss it here if you already have demo code. For a few other bugs I cuold not find repro code without a few gigabyte of sensitive data...
>>>
>>>Did you get responses?
>>
>>Status changes in the online bug list - on all of them.
>>Included in the "fixed" list - most of them.
>>Personal mail - twice, one of them here on UT.
>
>I'll give it another try then. Thanks.

I can confirm that the latest SP2 Refresh (16/10/07) has NOT , repeat NOT fixed this bug, but has re introduced it from VFP9. This was fixed in SP1 but has now reared its ugly head even in the "Refresh" of Sp2.