Hi Nadya,
I really prefer lots of little prgs for UDFs. Here's the reasons.
You have to know the name of the function you want to call, whether it's in a big file or separate. Make the name compelling and that's a good start. I hate dragging in every function I've ever found helpful for a Hello World app. It's preferable to just get what you need. More grainularity--good. If you also make things small, it's easier to find the chunk of code you need to inspect--at least that's what I've found.


>Hi Tracy,
>
>Well, all of you confirm my thought, that we need to consolidate those UDFs in something. For start, I think, I'll choose most used UDFs, like CreatePDF, for example. Then I would need to convince my colleagues, what we all benefit, if those UDFs would be put in our wgUtility program. This is the hardest part...
>
>>Hi Nadya, for UDFs that are used in many locations throughout an app or across different apps, I put them all into one common utility program. Those that are unique, I keep separate.
>>Tracy
>>
>>>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)...
>>>
>>>Thanks in advance.