Error trapping to avoid close-down

[wordmuse]

Assuming there's any movement on URP from a V5 paid user... for whatever that's worth to anyone...

I just did something that caused URP to hang, necessitating a hard quit of the program.

I opened an old UPR file created on another computer that died awhile back, but backed up and brought to life on my current machine. I clicked an item which was linked to a file on the old computer, but either wasn't backed up or is in a different location on the new machine.

URP froze.

Why not just trap the error and say, "File not found." Then I could dismiss the dialog and continue with my work. This freezing of the program is not helpful.

- Bal

[kinook]

Just checking the existence of a file on a network share that's invalid can be slow. That's just the way the Windows file access APIs work. It's not hung--it can just takes several seconds for the API to return.

[wordmuse]

Several seconds as in 10 minutes? Not a huge deal; just seems like there ought to be a way to clean up a data file without having to brute force click an item, hang the program, close it, restart it, right click the offending item and delete it. With over a hundred items, my only real alternative is to delete an entire section of the database and start over.

Before I go that route, isn't there anything else I can do?

Thanks.
- Bal

[kinook]

If all the items are pointing to the same network share, you could search the URL attribute, then hold down Alt when clicking on a result to prevent the item document from loading, then edit the URL attribute as needed.
http://www.kinook.com/UltraRecall/Manual/itemdetailspane.htm

Or see the SQL interface for making mass changes to an attribute.
http://www.kinook.com/Forum/showthread.php?t=2825

[wordmuse]

thanks - I'll give that a try.
- Bal