>Hi everybody,
>
>Yesterday I was totally lost in all different kind of programs, I created or found here and put in our CommonWg\Progs directory. So, I'm thinking, may be it's better to put some of them (which are used most) in our wgUtility.prg
>
>What is better in general: one big procedure or lots of small ones? Which approach do you use? Sorry, if this was asked before (may be even I asked it)...

Nadya,

One thing I don't think I have seen mentioned is source control. Splitting into a lot of files would make source control easier if multiple folks needed to change a lot of the functions at once. I realize we are talking about functions that don't change much, but if something would happen that would require a lot of functions to be changed, a single monolithic procedure file would be harder to share among developers in a controlled fashion. I realize that VSS supports multiple checkouts and then merges, but there's nothing simpler than separate files checked out by separate folks.

I actually use a mix of separate files and global proc files. I generally have a global procedure file that gets used across all apps, and then a specific function library for app-specific needs.

Good luck with whatever system you choose! And whatever you choose, try to stay consistent with it!

JoeK