>This might be a very basic question but I definately don't know the answer...
>
>When working with the form designer (or a project really), is there someplace that I can view ALL the code for ALL the methods on ALL the controls AND the form methods themselves?
>
>I have been spending the last 2 hours trying to research an problem in a form. Short of bringing up the object code window and selecting each object, one by one, then checking the procedure list for each one for highlighted procedures, then looking through that code and moving to the next procedure and then the next object... there has to be an easier way. Isn't there?


To see all the code in a form or class library, you can use the Class Browser. Open CB, then open your form in it. Click on the form's filename in the treeview, then click the "View Class Code" button - tooltips show which one it is. You can then save the text file, and use it for quick searches, reference, etc.

If your form contains objects from VCX's rather than VFP's base classes, you'll need to open and export those, too.

It sounds like you're hitting the *wrong* side of the double-edged sword of VFP's flexibility. You can scatter code in classes/classlibs all over the place and assemble them into a single form, which is very powerful and flexible. But if you do that, then by definition your code is NOT neatly assembled in a single place for easy reference, but is scattered all over the place, and *you* have to look through it one file at a time.

While I don't know what type of problem you are researching, I recommend tracing through the code and watching what happens that's undesirable/unexpected. About 90% of the time, I find that to be easier and faster than searching through code I didn't write, because I'm observing behavior *while it happens* rather than looking for clues in code sitting lifelessly on my hard drive.

If you can post what type of problem you're troubleshooting, maybe we can give more specific suggestions on how to track it down.

That being said, I have used the Class Browser export frequently for "quick searches" through code.