>>>>The business case is simple - no "workaround" is ever good "enough".
>>>>If "workarounds" have value when considering fixing a bug, then we are
>>>>getting further from the goal, not closer!
>>>
>>>If a two line workaround in code will do the same thing as 150-line fix (numbers pulled out of a ratty old top hat), that might break something else, I'll take the two-line workaround, thank you very much.
>>
>>And that really helps the poor developer who has struggled for a few days - and red-eye nights - had read and re-read the VFP documentation, and came up dry when searching the KB.
>>He has to find the bug before a KB article can even help him!
>>
>
>>Meanwhile, fixing the bug means he'll never even have to look for it in the first place.
>
>Considering that this affects at least five SET commands, not just SET DATE as stated in the KB and the problem being there since VFP 3!!!, should probably be sufficient enough for a real fix.
>
>I did use the workaround though. As if there is something else I can do.

It is beginning to look like the KB is viewed by MS as a legitimate antidote for bugs.

Yet even that is failing the grade, not only because of the inherent problems in treating the KB as bug fixes, but also because less and less is actually getting into KB articles.

You spent days and nights struggling with this one problem. Then, and only then, was a KB article of any value to you.
MS needs to learn that such events, repeated through countless VFP developers on a daily basis, are not acceptably dealt-with through KB articles EVEN IF a bug reported today is KB'ed tomorrow.