>>>Having a common utils.prg allows encapsulation, a single place to search for the function you need.
>
>We have used them for that purpose, but if I were refactoring? Certainly I'd consider Mike's and Tamar's advice- not least because for VFP Compiler, the last thing you want is giant baggage to be parsed and converted to C++ that's never even used in the app, but happens to be in a large SET PROC. It's worse if SET PROCS refer to each other, because then the simplest app suddenly can have a forest of library prgs cluttering things up.

It's a possibility. As I recall, it's only happened a handful of times, and it's easy enough to diagnose with a Code References search. It'll find duplicate definitions.

One of the biggest issues we've had have been with people using abbreviated keyword names, so we did away with that some time ago, so searching for "FUNCTION myFuncName" instead of "FUNC myFuncName" will always work.