>>>>What do you mean "call this function from SP" - do you want to call one stored procedure from another stored procedure?
>>>
>>>No, I just want to run the function from the database and make sure that VFP set path or set('procedure') is not searched to find this function.
>>
>>For instance, if I have it in SP and in the program that is in set('procedure'), the one from set('procedure') was executing.
>
>Check this:
>
>Visual FoxPro Invocation Stack
>http://fox.wikis.com/wc.dll?Wiki~TopicTextSearch~VisualFoxProInvocationStack
>
>Carlos

Carlos,

Thanks a lot. Well, according to this

Internal commands ( if the function is not prefixed with m.) and base classes, then

User-defined class definitions cached in memory in the order they were loaded, so long as the class definitions are still along SET CLASSLIB or SET PROCEDURE, then

If in VFP 8, a collection's default method, for example myCollection(), then

MyArray(n) array memory variable in scope.

Functions and class definitions in the current .PRG, then

Class definitions along SET CLASSLIB, then

Functions and class definitions along SET PROCEDURE, then

Functions and class definitions in the stored procedures of the current SET DATABASE TO, then

Functions and class definitions in the execution chain (call stack), then

Functions named for files bound in the app/exe, then

Functions named for files in the SET DEFAULT (local) directory, then

Functions named for files out along SET PATH.

COM classes in the OLE registry if SET OLEOBJECT is ON.

the function in set('procedure') would be called before database procedure.

My question is: is where a way to bypass this VFP internal search and tell the engine to use my SP?

Thanks again for your help.