>...I would create a separate file and call it my_ctod.prg. I have stopped using procedure files many years ago, much easier with separate files.

Most of our apps use a common utility.prg which contains the bulk of all functions we need globally. We also use stored procedures for those specific to the data. Our newid() function, for example, is always in the dbc so it's the correct one. But, our app_messagebox() function is in utility.prg, so it's a common one shared by our various apps.

I've always found it better to use procedure files for encapsulation of related things. For things like pdf3.prg, which are really stand-alone, it's better to have them in their own file.

My $0.000002 +/- :-)