OK, so right off I want to emphasize that this is a BIG and I mean very big PROBLEM. Aside from Bridge's painfully slow search feature - however robust it might -- the potential for a corrupt cache is very real, particularly for the archivist who is a heavy Bridge user.
You launch Bridge and when normally the program opens and stabilizes you see it stall out as it "builds criteria" even though you've selected nothing. That means its trying to access the cache of the interface itself and having a damn hard time doing it.
Then you get the dreaded message: "Bridge encountered a problem reading the cache. Please purge the central cache."
Oh no.
That means all the indexing you've done has to be trashed and you need to start all over again. Which also means that you are unable to search your image library in the process. That's not good.
Well, this has happened to me a number of times over the years and it's never pretty. While you can't prevent this from happening you can anticipate that it will and work around it.
How?
Always have the image library indexed on at least two machines. That's what I do and if you're using Bridge to manage an image library you should, too.
No comments:
Post a Comment