>>>Can you imagine someone saying: The FTP function does not work anymore, what are the most recent changes? You'll have to go through your source controls for 20 files in stead of one.
>>
>>Get a decent source control? This is a wiggle the fingers using git no matter how many files are involved. (If used gitish and not CVS like .... [gdr] )
>
>We have been using sourcegear vault for a decade or more. Its quite good. But the point is that dealing with one file is better than dealing with 20. No matter what tools you use.

We should create a new thread.

No it is not. At least it depends what I like to do.
I do not much with procedures, most logic goes by OOP. Most and largest prgs are defining non visual classes. So I can do a class per prg but then I need most of them at once, I do rarely change them, so what's the point in splitting them around? That some are use on a lesser frequency is no problem.

The FUNCTIONS (I rarely use procedures by VFP standard) are something the quietly works for an eternity is stored in some prg-libs for good. No need to touch them. What ever the reason was 20odd years ago, it is, and then I do not touch something working for better cosmetics. Done.

VCX's - now we come to the goodies. Since I heavy work with git and foxbin2prg the single classes of a VFPX go all in single files - because this makes the tracing of changes in git possible. And diff / merge would be a real pain if I would deal with whole VCX's (iow VC2, the text representation)

If somebody is used to changing something by MOD COMM proc_name.prg this is all fine, nice, ok. I like the single lib open in an external program, with split view, and know how to use the search functions there. This is a matter of style and nothing else.

It's simple a sign of growing old if one insists in own style as the one and only. I know that I belong to to youngsters on VFP. ;)