Thanks, John
I do use the UT forums for just this type of thing once I have exhausted my own resources and still have hit a wall. Normally, I can get resolution or a workaround in short order. I'm not one who immediately cries "BUG" because I know from experience that in most cases it is a dumb coding error or misunderstanding of what something is supposed to do that I have made.
I certainly understand the business reasons why a public list of open issues would not be a desirable thing for MS and as I said, I really don't expect this list to ever appear. However, I will take this opportunity to express my appreciation for the excellent work that you and the entire development team do in providing timely answers in this forum as well as making VFP one of the most powerful and stable development tools available. Thanks and keep up the good work.
Elmer
>Hi Elmer,
>
>Mike Stewart, Jim Saunders, me, and other technical members of the VFP Team are monitoring the UT constantly. If you find something that you think is not working right and post a message about it, chances are that one of us will respond and acknoeledge whether it's a bug or not or suggest a workaround. If it's not, chances are that a member of the UT commmunity will give you a fix or explain the issue.
>
>
>>
>>I understand that it may not be advantageous to MS to openly admit that there are open issues or "bugs", but it would surely help developers like me who may run into a problem and spend countless hours analyzing code to only to find out that it is a bug that requires some workaround, and then devise my own workaround when someone else may have already done that. Admittedly it is a rare occurence, but I have spent many hours doing just that as I'm sure others have as well. If I could look for a known issue and suggested workaround, it would certainly make my life easier when something like this happens. It would also eliminate numerous duplicate bug reports from different developers when it is already a known issue within the development team. If the community maintains a list somewhere that can be referenced, that will work for me, but I believe that an centralized official list would be of more value to everyone (not that I expect this to happen).
>>
>>>Hi Elmer,
>>>
>>>Glad you like the list. However, it's unlikely that we'd post a list of open bugs until we'd either fixed them or rejected them. It wouldn't be practical for many reasons - I hope you understand. There is some discussion about exposing open bugs to the community that were found by the community but nothing concrete yet.
>>>
>>>
>>>>This is great!!! Everyone who has been requesting this list should be pleased. We all definitely should click on the "Provide us with feedback on this article" link to express our delight in finally getting it and how useful it is to the community. Perhaps we may someday see a easily accessible list of current bugs in the queue awaiting fixes with suggested work arounds without having to trudge through obscure KB articles.
>>>>
>>>>
>>>>
>>>>>Well that should be fix listS.
>>>>>
>>>>>Feast your eyes on the following, my UT friends:
>>>>>
>>>>>
http://support.microsoft.com/?id=818175>>>>>
http://support.microsoft.com/?id=818178>>>>>
http://support.microsoft.com/?id=818179>>>>>
>>>>>I still haven't finished reading them, but this is too good to keep to myself.
>>>>>
>>>>>ENJOY!
