Thank you for your reply.
- Yes, If a new user was created the COM object and opened database we was locked a special record in the external table. We was tried to add a timer object in COM Dll and checked for a locked record in a table. But an event of timer “OnTimer” in COM Dll don’t work. We check it. We don’t know what to do.
We tried to kill a thread in process (dllhost.exe) in which created our COM dll, but can’t found needed thread and just can to kill a process and don’t solve our problem.


---------

Have you thought about adding a code to the COM DLL to check for a "flag" file and shutdown (close databases, etc) if the file is there? Of course it would require that COM DLL would have a timer object and check for the "flag" file periodically.

Just a thought.


>Multithread dll was written on Visual FoxPro 7.0 and was registered as COM+ Application on Win2000 Server. An object of this component is created on a remote computer (client) in local network. Multithread dll opens a database on the server and performs queries or other procedures. The base is closed and the object is destroyed on the client after work is finished. It’s clear and correct.
> But if between a client and the server something bad happens, like problems with local net, the database on the server stays opened by the COM+ object. So we can’t open database exclusively to perform reindexation or something alike until the object is destroyed and the database is closed. We cannot destroy it in conventional way because the creator is disconnected and don’t have access to the server and so -- to the object. Win2000 destroys the object automatically in 11 minutes (experimental data). But it is too much – system administrator may want to open the database exclusively at any time!
>
>Looking in Windows – Administrative Tools – Computer Management – Open Files we can see that the user has opened files of the database.
>How to force Windows to close these files? Or any other ideas how to resolve the problem.