I'll second that emotion - for the most part.

1. Don't know if I agree with that - mainly because I fall squarely in #2 camp, having used VFP5 debugger maybe 4 or 5 times in over 2 years. WAIT WINDOWs seem to be all I need. The majority of non-trivial bugs I encounter in my apps are MSKB material.

2. through 5. Agree.

6. Some might argue that it could fit into "Troubleshooting", but that category tends to get hijacked by people with IIS and SQL7 issues, Novell Client32 problems, etc. etc.

I would also like to see information on the practical use of DEBUGOUT and methods for logging event firing sequences. BTW are there any good articles and/or FAQs here on any debugging topics?

>Why?
>
>1. It is a crucial tool for being an effective programmer
>
>2. It is seriously underused by many programmers
>
>3. There are idiosyncratic ways of using it that are useful to share.
>
>4. It is a discrete module, as much as reports and libraries, that is extremely powerful, and, see 2 above, it is underused.
>
>5. It is weird and difficult to get comfortable with for many folks.
>
>6. There is absolutely no other category it usefully falls into. General doesn't cut it for me. It is not VFP General information.
>
>I welcome your opinions and look forward to reading them.