>>>>
>>>>The question is, what takes precedance, if you have x function in Procedure file, in fll (dll) or as a stored procedure and how you can explicitly invoke the needed one.
>>>>
>>>>I believe, this is a case, which doesn't have a solution except for renaming...
>>>
>>>Thanks for description Nadya :)
>>>My current solution is like this (renaming is far more harder on live data around the world, and no existing field could set as default) :
>>>
>>>

*DBC is currently open and selected one
>>>lcDummy = sys(2015)
>>>create table (lcDummy) (dummy l,mySPCaller i default x())
>>>*A loop
>>>insert into (lcDummy) values (.f.)
>>>RetVal = eval(lcDummy+'.mySPCaller')
>>>*end loop
>>>use in (lcDummy)
>>>drop table (lcDummy)
>>>erase (lcDummy+'.*')

>>>
>>>Cetin
>>
>>Interesting. Why in this case it automatically takes x from Database and not another x? What if your x uses field values? I'm afraid, this code is not 100% reliable.
>
>It's by design :)
>
>Update: I don't know a single line of code that's 100% reliable :)
>Cetin

LOL ;)

Even more update: I don't know a single entity in VFP code line that is 100% reliable ;-)