Announcement

Collapse
No announcement yet.

Changing the location of the Database file.

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

  • Changing the location of the Database file.

    I am evaluating Pro 2023. Under the menu 'Options', I can change a few folder locations, but not the 'Database file'. I keep a well organised folder structure, moving all data randomly dumped under the Users folders, to C:\DATA. How can I do this for ACDSee?

    Am I correct that this is the base folder for all of the database data?

    I am only interested in managing my collection of photos. I am changing from an old program that is now discontinued.

    I have exported all of it's database text, whch is now in Excel format. I understand that ACDSee uses .XMP files, so is it possible to import these files into ACDSee?

  • #2
    Originally posted by Landyman130 View Post
    I am evaluating Pro 2023. Under the menu 'Options', I can change a few folder locations, but not the 'Database file'. I keep a well organised folder structure, moving all data randomly dumped under the Users folders, to C:\DATA. How can I do this for ACDSee?

    Am I correct that this is the base folder for all of the database data?
    The default database location for 2023 Pro version is C:\Users\YourName\Appdata\Local\ACD Systems\Catalogs\160Pro\Default
    With ACDSee closed, and using Windows File Explorer create a new folder at your chosen location, for example "MyACDSeeDB", then:-

    1/. Copy the "Default" folder into "MyACDSeeDB).
    2/. Also copy the file C:\Users\YourName\Appdata\Local\ACD Systems\Catalogs\160Pro\Default.dbin into MyACDSeeDB
    3/. Rename the copied folder Default to a name of your choice (for example "2023DB"), and rename the copied file Default.dbin to the same name, for example "2023DB.dbin..

    Restart ACDSee, go to File\Database\Open and in the Open Database dialog select the above file "2023DB.dbin" then click on Open.
    ACDsee will then restart on the copied database.

    Alternatively you can simply start a complete new database (File\Database\New). That will leave the old database as is, and available to reconnect to if required. You can switch between multiple databases.

    Edit: Whilst that I hope answers how to move the data base, ACDSee maintains quite a number of files under the ACD Systems folder in Users\Appdata\Local. AFAIK there is no provision within the program to change the location of them.

    I have exported all of it's database text, whch is now in Excel format. I understand that ACDSee uses .XMP files, so is it possible to import these files into ACDSee?
    No, if you choose to embed ACDSee metadata in your images, ACDSee will create xmp sidecar files for each image where the image format doesn't support direct embedding of xmp metadata (for instance RAW images), but the database fields are not xmp.

    You can import a list of keywords from a text list (Tools\Metadata\Import Keywords, but you would then have to assign them to the images.

    ACDSee automatically adds entries for the images into the database as you browse their folder in ACDSee (and that will include EXIF, IPTC and some ACDSee metadata if embedded in the images. It can also do this whilst ACDSee is closed and the computer is idle if you set up the Indexer (Tools\Options\ACDSee Indexer).

    ACDSee can import database entries from a Lightroom Database (Tools\Database\Import.\Lightroom Database).
    It can also read embedded EXIF, IPTC and ACDSee metadata from the images if you use Tools\Database\Catalog Files. The catalog process also reads in ACDSee Face Data if embedded, and can read read embedded LightRoom or Picasa Face Data.

    Take the time to read the help file for the intended task before you action it..
    Last edited by Greyfox; 03-07-2023, 10:14 PM.

    Comment


    • #3
      Originally posted by Greyfox View Post

      Alternatively you can simply start a complete new database (File\Database\New). That will leave the old database as is, and available to reconnect to if required. You can switch between multiple databases.

      Edit: Whilst that I hope answers how to move the data base, ACDSee maintains quite a number of files under the ACD Systems folder in Users\Appdata\Local. AFAIK there is no provision within the program to change the location of them.

      Take the time to read the help file for the intended task before you action it..
      Many thanks Greyfox for your detailed response.

      Since starting this topic, I have purchased a licence as the program will provide much I desire. It may lack certain features that I would like, but discovering if they exist is time consuming.

      I have viewed many of the 'ACDSee Photo Studio for Beginners' videos but they are mainly promoting their author, lacking the 'how to do' necessary to use a feature. But at least it makes one aware that a feature does exist. An example being 'Keywords'. I've setup a few, but now need to know how to keep them visible when re-starting ACDSee.

      I have used the program's help, but need to spend much more time there!

      I use 'ViceVersa Pro' for all of my backups, so can easily add the ACD Systems folder you mention. VVP has incremental backup to speed-up the process, so embedding data into image files would seriously lengthen backups and massively increase it's archive of replaced files, so I won't be using those features of ACDSee. I keep my master photo collection on a 2TB SSD C: drive. Photos backup goes onto two USB SSDs, used solely for photos. All of my data (including photos) is also backed-up onto three USB hard drives.


      Thanks again.

      Comment


      • #4
        Originally posted by Landyman130 View Post
        ....so embedding data into image files would seriously lengthen backups and massively increase it's archive of replaced files, so I won't be using those features of ACDSee....
        Just a comment based on past experience..

        Yes, embedding the ACDSee metadata in the images does increase the size or the archive, however that has to be weighed up against the benefit of the safeguard it provides.

        Database backups are OK as far as they go, however the weak spot is that a gradually developing database issues will be carried over into the database backups, and when it subsequently becomes necessary to replace the database, the only current backup may contain the same issue.

        Over the years, being able to start a brand new database, and read back the metadata from the images into the new database has for me been well worth the extra storage space.

        It is also perhaps also worth noting that the "Remove Orphan Folders" in Database Maintenance, which deletes any out-of-date or broken references to missing files or information for the selected folder does not work (and is greyed out) for folders located on network drives​. (See Help file, "Maintaining the Database").

        Being able to remove all database entries for such drives, and then read back the information from the metadata embedded in the images via the Database/Catalog Files provides a solution.

        Comment

        Working...
        X