Hi Tracy,

sorry it didn't work out...

Your mentioning "it breaks when built into an app"
set me on this trail. And I am not totally sure if my gut identified the problem, but I gave you the wrong check.

For instance we had a screen called by a prg
fkfteile.prg in an app "kfGrund".

which worked fine, as long as you hadn't opened
the kfreport.app, where a function fkfteile was a subsequent
function in the kfreport.prg.

Afterwards the fkfteile.prg was not found
by DO fkfteile with ...
by a program in kfGrund, but the function from
kfReport.App was run.

Since this resulted in a nice crash,
it was easy to find and fix -
I worry about similar functions doing nearly the same
thing in many programs (and not crashing),
since that was the "template pattern"
of the fpw-programs.

You specifiy the function names in the screen.
Any chance a function called from the search to finding
has a name used somewhere else ?

Either check with the debugger inlist(lower(program(), "","",)
or analyze your code programmatically or via foxdoc.

HTH

thomas