>>>>

IF you have a question
>>>>  IF you have tried the community first
>>>>    IF it is about a presumed bug or lack of documentation
>>>>      IF you suspect that it can only be answered by a member of the vfp devteam
>>>>        IF you are not an mvp
>>>>          What do YOU do?
>>>>        ENDIF
>>>>      ENDIF
>>>>    ENDIF
>>>>  ENDIF
>>>>ENDIF

>>>
>>>Fornutaly this doesn't seem to happen to us VFP guys too often. The few times that it has..I simply found another way to write what I was working on.
>>
>>Are you serious here or rather just cynical.
>>
>>If you are serious here, you either use only the portion of the language that is teached to the starters and the intermediate, or you are brilliant. In the latter case, please let us know in future your ingenious workarounds.
>
>Actually I was being serious. The reason I said this isn't because some brilliant ingenious VFP person, it's because VFP is a mature product and there is a lot of documentation - so these type of unanswerable questions don't seem to pop up to often.

Last week I had three consequtive days with a bug a day. And this wasn't really one of the worst weeks. Or are you siding with Marcia and suggesting that those who regularly report bugs are likely merely bad programmers?