Well, there's the repository viewer, which can show you where various operations on the component can be called from (assuming you have the cross reference stuff turned on when compiling). You could (presumably) build something from this data which could find all the components which call all the components which call your target component, but it's going to be complex.  Within the runtime you can use the $proccontext("STACK") to give you the current path to the point you are at. 

Hi dammie, not quite sure what you mean by "run path to component". Perhaps an IOprint for opening non-dbms files (/pri=64) can help ? See: https://unifaceinfo.com/forum/uniface-10-enterprise-edition/license-types/#p6053680