>>VFP finds the function in the order of the SET PROCEDURE commands. This is why I'm of the
>>mindset that when you subclass something, call it a different name. And incidentally, I
>>haven't used a procedure file since the days of 2.5, again, for this very reason. Too confusing.
>
>Ahh, but VFP (or FP) will not find the expected (at least as I see it) proc/func if there are 2 same-named items in the same .PRG. It will use the last one encountered.

Have not tested recently, but this one about the only area where FP was better than vfp:

If you have different prg's with subfunctions/procs in you app - NOT all sub-procs made visible via set procedure, those sub-prcedures meant only to be used for the calling program on the basis of the defined search path (module functions if you like) at least vfp6 sometimes used the wrong procedure, while FP picked the correct on. Verified when porting a large FPW app where a kind of template-pattenr was used in each module and I had up to 48 functions with the same name. Terrible by today's standards, but in FP an attempt to sturcture method naming via one of today's most simple patterns. Had not check on this particular insect lately...

regards

thomas