>(0) please define 'outside' and 'inside' the application
>
>Inside by way of timers or a coverage log of an area with many calls to the function in question.
>
>Outside by way of setting procedure only to the library of the function and calling it in a loop. One possibility is that Fox caches the function when it's called repeatedly but un-caches it when it's being called in the application since in the application we have lots of code called between each call to the function.

Oh, and I do not think that the 'outside/inside' is the reason

You could replace GetMyInfo() by m.GetMyInfo()