![Quote](images/misc/quote_icon.png)
Originally Posted by
Colin Southern
Hi Frank,
My standing advice with LR is "be careful about where the edits are stored" - if everything is stored in 1 database then that's one heck of an important database! I purchased and looked briefly at LR3, but for me, it didn't suit my workflow as well as Bridge did -- what I did feel FAR FAR FAR FAR more comfortable with though was having image edits stored in the same DNG file as the image data (which LR can do to - it just needs to be told to do it) - that way if there's ever an issue with a LR catalog / database one doesn't lose image edits (I know backups are the "answer" (in theory), but having been involved with IT all my working life, I also know that the theory and the practice don't always align very well (like how databases can be corrupt - but folks don't always know because they're not checking old data - and when they DO discover a corruption they find that they've already over-written the backup sets done before the corruption occured. Or they don't ever test backups - and discover (at the worst possible time) that their backups aren't as stable as they thought (I've personally had that one bite me in the bum big time)).