>Does it makes a different in having all the procedures in a file then to break them up into pieces?

There have been several opinions expressed here, each having its own positives and negatives. I believe that you should do what's most comfortable for you. Nevertheless, here's my 2 cents (US).

It may be true that creating a procedure file containing all the commonly used procedures and functions may not be quite as fast as having them as individual files, the performance hit is simply (in my experience) not worth even mentioning. If a system has performance problems, it probably stems from other reasons.

Further, the notion it somehow easier to access individual files rather than the procedures and functions in one is strictly a matter of personal preference. I fail to see how it's either easier or faster for me to go to the project manager and find the desired program file than it is for me to right click in the procedure file's edit window and select the module from the Procedure/Function list.

As for creating a non-visual class, that's the pure OOP way to do it, but this too has some drawbacks. You have to recreate the file as an object, plus the idividual methods take slightly longer to call. However, as with using a large procedure file, this performance hit really isn't even worth talking about.