decreasing danger of losing work on externally edited stored files

[UR user]

I've been away from UR for a while, but I'm back using the program.

Back then, there was one way that if you aren't careful, you could lose work.

1. Open UR
2. Open a stored file (e.g. Word docx) and start editing / saving within Word regularly, etc., thinking everything's ok.
3. Close down UR (not realizing that the Word file is still open)
4. Still work on the Word file for another hour, saving regularly
5. Close down Word
6. Next day.... Open UR to find out that that last hour's worth of work is gone (because UR had been shut down prior to further work done on the (temp) Word file that had been opened).

I realize that this can be avoided by making sure that UR is never closed while externally editing documents. But if you have dozens of UR databases open (and closed) and dozens of windows opened and closed during the day (some with stored docs and some not), then there will be human error.

Assuming I have described UR's operations correctly, the problem can be solved in this way:

* Anytime a UR database is closed, it should check whether there are any stored files that are being externally edited. If so, it should warn the user about the potential for data loss. Frankly, UR shouldn't even let you shut down the DB without first closing the stored file that is being externally edited.

This can't be that hard to implement. What do you think?