>>>The downside - for me - to place each function/procedure in a separate .PRG is a maintenance headache. I have not counted but the application probably has a couple of hundred procedures. And having to scroll through this list in the project manager (if necessary to look at the code of whatever), would increase the time of maintenance. I know many will say that instead of the Functions/Procedures I should have them in classes. And maybe so. But I started this application way before I knew anything about how to build classes. When I can and when it makes sense, I do refactor the code.
>>
>>Why would you use the Project Manager to find a particular file? If I'm looking at a routine and it calls something and I want to see that, I use my keyboard shortcut for Thor's Go To Definition tool and it just opens. If I need to edit something and I know what it is, I just type MC and the filename in the Command Window. It's really rare that I need to look at a routine and I don't know its name. Does that come up for you a lot?
>>
>>Tamar
>
>What if you have a large project producing 40MB exe with countless classes and functions?
>I can't possibly know all functions, procedures, classes and method from the top of my head. There are way too many.
>The project manager and GoFish are my friends.

I've just never found the Project Manager all that useful. GoFish and Go To Definition I use every day. Once in a while, Finder is a better tool for what I need. At the moment, I rarely need to build EXEs. (Someone else does that for the main project I'm on.) If I did, I'd switch to Project Explorer, which seems far better for things like finding relevant files.

>I might have an approximate name, looking through the PM ussually will find me what I need.
>
>But all in all, I'm not using the PM that much. Most goes through the command window.

In that, we agree. As I said, I only open the PM when I need to build.

Tamar