Versions 2 and 2.5 have some bugs which mean that people sometimes have to delete the database and rebuild it. (I realise there were ways to try to recover lost data).
A simple question - has this been fixed in V3?

Versions 2 and 2.5 have some bugs which mean that people sometimes have to delete the database and rebuild it. (I realise there were ways to try to recover lost data).
A simple question - has this been fixed in V3?
Bugs will continue to exist in all versions, I'm sure. Some get fixed, new ones show up. It's the nature of software.
But if you've embedded your db in your files - as has been possible since 2.5 - then rebuilding the db is as easy as running a single command (Catalog Files).
FWIW, I haven't had to rebuild a db once since Pro 2 came out.
I recently had to DELETE my ACDSee database in PRO 2.5, because it was taking up too much space and slowing things down. My photos flow 'thru' my computer, and I create and delete folders (after backing up) on my working machine on a daily basis. ACDSee appears to keep info on photos and folders I have deleted - resulting in lots of irrelevent information after a few months.
Once I deleted the database (manually), ACDSee 2.5 re-started nicely and the 'slowness' disappeared.
This is true if you don't use ACDSee to do the deleting. Note that you don't have to delete the whole db in order to remove info for deleted file; just run database optimization with the option to remove orphans checked.
Subscribe to this topic via RSS
This topic has been closed to new replies.