Basically, the only way to break this link and be sure about it is to kill other processes from yours. There are various ways to do this, that have been pointed out, but a better question is whether you should.
I recommend looking into a try
-catch
pattern and making your application report the error to the user, instead of aggressively trying to delete a document which may be open for a very good reason from the perspective of the user or even the system itself.
Also note that killing outside processes is not a garuanteed solution, as there are multiple cases where the "kill outside process" step could fail (targeted process is run as Administrator and your app isn't, targeted process it set up as a Windows Service and restarts itself before you finish deletion, targeted process is a system-critical process which can't be terminated, ect.)