>>Nadya,
>>
>>One thought did occur to me. You mention that you have stored procedures by the same name in different databases. VFP may be caching the first one called in memory, the same way it would do with a regular program (prg). Afterall, stored procedures in VFP DBC's are nothing more than compiled Fox code. If it is doing this, it may lead to the wrong code being executed. If so, it might, to some degree, explain the inconsistent results you're seeing. To test this, you could try the same code with and without a CLEAR PROGRAM issued after the call to the stored proc.
>
>Thanks, George. This explains some problems, we're having. It's very important, so I send it to all my team members. Too bad, I had not started this thread, so I can not award you :)

Thanks anyway, Nadya. Remember, however, that this is pure speculation on my. It may not be the cause. While I think it highly likely that it could be a problem, I can't say with any certanty. Only you can answer that question.:-)

>For the particular application, I already renamed this procedure to something else.
>
>Thanks.

You're welcome.