>It is depended on the way you call this COM object. For example, imagine situation when you call the COM object to request a lengthy operation for it. After that in some other place in the program you try to call the COM object again to get another data and cannot, because COM object is busy working on previous task. As far as client application aware about such thing, no problem.
>
>There are no otehr issues as far as I know.



No no, this is ment to be as an independend instance for Background-
jobs like Data-Exchange etc. on a scheduled basis

The jobs will take max. a Minute or so. And in order to be sure I
always do add a flag .l_Busy that is .T. as long as a task runs.