Hi David,

(know the full answer without stupid keyboard mistakes by me)

you described only half of the problem.

VFP will execute function calls to functions
sporting the same function name totally different
to FPW when a later loaded App also has the function
defined AND the intended function is NOT in the stack.

Example:


Kfmain.App
KfMain.Prg
(Do KfParts)
KfParts.Prg

KfReport.App
KfReport.Prg
KfParts()

If KfMain calls KfParts the first time, everything will
work "as you used to know".

If you issue a call to KfReport, KfReport executes and is released
from the calling stack again, the next call "Do KfParts"
will execute the function defined in KfReport.

Since the execution order for "bound" programs is never
specified (to my knowledge), I can't call it a "bug",
but as you say, it breaks backward compatibility.

But since the remedy seems to be quite simple (after
a demo app showing that the stack calling chain is still
"honored"), I won't hold my breath for a "fix".

And since the "warning" abaout duplicate function names
has been included for quite some time in the doc's, I believe
it would break method overloading or someting now basic for VFP,
since it never has been fixed while beeing a nuisance for the
developer with "ancient code".

regards

thomas