ACDSee Pro 3 Beta - Bugs

Back to Topic OverviewPost New Reply

Re-embedding Database Information on upgrade

[closed] (5 posts)

Tags:

  • SteveCop
    Member

    After installing Pro3, it proposes embedding database data for my entire collection - 30000+ files. Obviously it does not/cannot know that all the files already have the database information embedded but I think that re-embedding is risky. The embedded data is a long-stop option to recover database data in the event that the database becomes damaged. Surely such a massive operation as converting the entire database from 2.5 to 3 is a prime time for problems to occur that might not be noticed initially. If you have allowed the program to re-embed into all files then you have taken away the possible recovery route.

    Would it not be possible to have an upgrade option that tells ACDSee that you have already embedded data in all pre-existing files as at the point of upgrade so that it only flags files that you work on from that point forward as requiring data to be embedded?

     

    Posted On May 30, 2009 - 07:06 PM (5 months ago) (Permalink to this post)

  • Marc Sabatella
    Moderator

    Thanks for the heads up!  I was preparing to embed all my info using 2.5, but I might hold off until we hear something about this.

     

    Posted On June 1, 2009 - 07:02 PM (5 months ago) (Permalink to this post)

  • fonebone
    Member

    I have noticed the same issue (50'000+ pictures in my case) and would prefer if re-embedding would not be necessary after the upgrade to Pro3.

    Posted On June 1, 2009 - 07:47 PM (5 months ago) (Permalink to this post)

  • ronser
    Member

    When I selected images to test in Pro 3 that were already imbedded from Pro 2.5 I copied them to a folder and then moved them to my database folder within Pro 3 and ran Catalog Files. I checked under Imbed Pending in the Organize pane and no file needed imbedding. So far I have not seen any problems. I did not elect to have Pro 3 convert any of my files at startup.

    Posted On June 2, 2009 - 12:05 AM (5 months ago) (Permalink to this post)

  • Marc Sabatella
    Moderator

    That makes sense.  Images that enter the Pro 3 db by means of "Catalog Files" from previously embedded info would not be likely to need embedding, whereas images that enter Pro 3 by means of Convert Database might.  Still seems the conversion operation and/or embed operation could somehow check that, but maybe there is some reason why it can't be done?  Or maybe it will be fixed by release?

    Won't be an issue for me, it looks like, because I have no intention of convertion my 2.5 db - I plan to use embed in 2.5 and catalog in 3.0, as I mentioned.

    Posted On June 4, 2009 - 06:13 PM (5 months ago) (Permalink to this post)

Subscribe to this topic via RSS

Topic Closed

This topic has been closed to new replies.