>I apologize if this answer can already be found in the archives. I no longer carry a full membership here at UT.
>
>We're running into a problem with slow function calls. While most problems of this likeness can be solved by simply making the function faster, the code inside the function executed alone is actually faster than the time it takes to call the function.
>
>4000 calls outside the application = 0.3
>4000 calls inside the application = 3.0
>
>We've put numerous timers on this to ensure that the slow part is the actual calling of the function and not the code inside.
>
>I figure at this point someone out there has run into this. If you stumbled onto a solution I'd love to hear it.
>
>Thanks

Is this function a part of the procedure library? In what order the classes/procedures are loaded in memory?