>>I have been asked about what would be the best way to externally shut down running FP apps. That is, an application ( probably VB ) that would inform users on a network who are currently running a FP app to shut down the app, and if they do not in a specified amount of time, then the VB app would forcefully shut down all running instances of the application on the network. How could this be done most gracefully, closing tables, cleaning up, etc. to keep from corrupting the open FP tables. The existing FP apps cannot ( or will not :-) ) be modified.
>>
>>Thanks,
>>Bill
>
>I hate to disagree with Ed, but from what I understand, DestroyWindow won't work with other threads. In other words, the only application that can use the function would be the current one on itself. That what the documentation says. In reality, however, it may actually work.
>
>I'd recommend using SendMessage() to issue a WM_CLOSE (16) message to the application. If you want more details, let me know.
>
>hth,

Hi George,

Thanks for the reply ( you too Edward ). I will look into this and I may have other questions concerning the specifics.

The request is actually for a friend who was asked to create a VB app to do this. I basically told him that, if at all possible, he shouldn't be externally shutting down network database apps due to the possibility of table(s) corruption. However, like all of us, he is in the situation that "the client gets what the client wants." If he HAS to do it, my concern was how to accomplish it as gracefully as possible to eliminate ( reduce? ) the possibility of corruption ( with the attendant corruption of his good name :-) ).

Thanks,
Bill