Announcement

Collapse
No announcement yet.

Trouble converting database

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Trouble converting database

    What would happen if I delete my "C:\Users\jbell\AppData\Local\ACD Systems\Catalogs\160Pro" folder?
    I am having trouble getting the face/people tags to appear in Pro 2023. I just upgraded from 2022 and have tried all I know to do (convert db, catalog, etc).
    The 160Pro folder is 50 times larger than the 150Pro folder!

  • #2
    Originally posted by JBell View Post
    What would happen if I delete my "C:\Users\jbell\AppData\Local\ACD Systems\Catalogs\160Pro" folder?
    I am having trouble getting the face/people tags to appear in Pro 2023. I just upgraded from 2022 and have tried all I know to do (convert db, catalog, etc).
    In that folder (C:\Users\jbell\AppData\Local\ACD Systems\Catalogs\160Pro) there should be a file called Default.dbin and a sub-folder named "Default" which will contain the default database from the installation, but subsequently updated by the entries read from the old database, converted and written to the default database (that assumes you haven't created a new database at a preferred location. If you have made any database backups with U2023, there will be another sub-folder called ACDSeeBK.

    I would not delete the parent folder. For the moment I also wouldn't delete the Default sub-folder (the current database) (and the .dbin file that refers to it.)

    What I would suggest is opening ACDSee Ultimate 2023, and in Tools\Options\Manage Mode, set the home folder to a folder on a local drive that has just a few photos in it. then click on OK.

    In Manage mode, from the file menu, choose Database\New. In the dialog that opens you will note that the default location will be C:\Users\jbell\AppData\Local\ACD Systems\Catalogs\160Pro". You can change this, but if that is where you want it to be, then just give the new database any name other than "Default". You can for instance call it "Default2" if you like. then click on OK. ACDSee will restart on the new database, and on the Home folder set above.

    You will then be on a completely new database, and you can then either run the convert database again to update it from the older version records, or use the Database\Catalog Files to read the information from the metadata embedded in the images. If you choose the latter, then make sure you have the appropriate settings ticked in the Catalog Files dialog. From memory in the Import from Cataloged Files section, by default Face Data is not ticked, but should be if the images have that metadata embedded. Also from memory in the File formats section the default is to Catalog only images. If you have videos I would choose the option to "Catalog images and videos". In the options section I would tick only "Build and include thumbnails in database". In the dialog, you also have to add the Folders to Catalog.

    When you get the new database up and running, then by all means delete the "Default" folder and the Defaut.dbin file that refers to it.

    The 160Pro folder is 50 times larger than the 150Pro folder!
    That should NOT be the case. If you start with a new database, then add in the entries from the 2022 Pro database, either using the conversion, or the Catalog method, then I would expect the database to actually be a bit smaller, primarily because the size of the ACDSee thumbnail cache at that stage is likely to be smaller, (and that is certainly the case here with the Ultimate versions.
    Last edited by Greyfox; 09-22-2022, 11:48 PM.

    Comment


    • #3
      I thought I should return and explain how I resolved my trouble. As it turns out, I was converting the wrong database! I had started with ACDSee using Home 2022. Then, needing another feature, I upgraded to Pro 2022. The whole time I was using Pro 2022 I was unknowingly still on the Home 2022 databse. So when I upgraded to Pro 2023 and converted the Pro 2022 database I wasn't getting the data I had added (unknowingly added to Home 2022).
      Before I discovered the errors of my way I had already started cataloging all the files into Pro2023. So, at least I figured it out and will start off Pro2023 with a good clean database.
      Thanks to all who helped, especially Tristan H & Greyfox

      Comment

      Working...
      X