You cannot - that is a problem. That is why it is recommended to test object first as usual VFP custom object, not as COM object. Then try to run it as COM after complete testing without COM. So run it client-side first. If you cannot (because SQL Server access or whatever reason), then you have to think about some sort of logging of commands and time at which they run. Thi way you will see in log file the sequense of commands ran in COM object code and see the point where delay happens. This way will not help you to spot a single command, but it will for sure help you to narrow down the place where problem happens. In addition, include debug information, and make error handler using Error event of the object. In Error handler write as much information into the log file as possible, include LineNo, program() etc. to see exact place where error happened.

HTH.

>Vlad, thanks for a good direction to play with. I think the parameters are the problem. I may try to run it as SP with parameters object instead of sinple SP call.
>By the way, how I can run and debug my com object on ther server, and see what cause the problem, as you have mention, it's a shame to admit but I dont know how can I do this.
>Meni treba poyasnyty ya ce vono debagaetsya.