David,

>I base in on being a beta tester of VFP since VFP3. As well as what Randy has posted with regards to what makes a good bug report. Do you comprehend that what Fabio "sees" might not be seen under every O/S or video configuration? And that words describing the fault are much better than drawing arrows. So what does that arrow on the left side mean exactly? You can not say with 100% assurance, not unless you are looking over his shoulder right now. Does Fabio's display also have a break in the drawing of the pageframe border there too? Or does he have a break on the leftt side and not the right? Does he see some other sort of problem? based on his bug report, no one but him knows what he sees or doesn't see.

If there is any question about any bug, there should be communication. It might be put there by accident or because of his configuration. I don't know for sure. Even with a well documented bugreport you could still have questions.

Then the proper step would be: ASK. and not DISMISS the bugreport as USELESS. This is called CONSTRUCTIVE critisism instead of DESTRUCTIVE. By definition it is not useless because he clearly identified a bug. I get bugreports from my clients and almost none is as clear that I can solve it without any additional communication. If you insist upon only handling clear and under all conditions reproducable code you're putting your head into the sand.

Bottom line, was it a useless bugreport? No. Could it be better? Probably yes. Was your way of reacting inappropriate? Certainly yes!

I don't agree with all Fabio is proposing either or issues he sees as problems, but one thing for sure, he thinks a lot more about issues and VFPs weaknesses than I've seen a lot of prominents do up here.

Walter,