>>>What prevents you from doing coding in VFP7 and debugging and testing in VFP6? :) I worked this way for a while until we moved to VFP7/8.
>>>
>>>BTW, if MS KB says, "We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available", it means that no fix should be expected. :)
>>
>>I hope you are kidding (at least that is how I understand your ":)").
>
>Not really.
>
>>Because if they don't fix this problem and the problem discovered by Igor in this thread, they won't see my money :-).
>
>I think you would hurt yourself more than MS with this decision. :)
>
Tell me how? :)
>>As far as testing and debugging. I am happy if I have time to test for my own bugs. I certainly don't have time to test for VFP bugs.
>
>I'm not following you on this one.
What I mean to say is when I write code using SEEK() function I expect it to work (whereas it does not work in some cases - e.g. Q190496). If my customers would not tell me that the data is being messed up I would never came across this bug. But I didn't test for this bug initially, this is what I meant.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
