C1P opens database copy instead of current database
Capture One opened an old copy of my database instead of the latest version after copying my cocatalog package to a new hard drive and clicking on the cocatalog located on the new drive. This can be confusing, but can be corrected by removing the old copy. Details, below:
After copying my database (.cocatalog package) from one drive to another, I clicked on the new copy of the .cocatalog package and the database opened from the new copy was over 200 hundred images short of the original and the recent import lists was for earlier dates ending well before the latest imports. It turns out that the package contained an old copy of the cocatalog.db database (with the word COPY inserted before the database name) along with the one that usually opens. When selecting the cocatalog package Capture One selected the copy of the database from the package instead of the latest version. As it happens, the database "COPY..." can be deleted forcing Capture One to open the most recent database.
I have referred this to C1 support with the following questions: What causes a copy to be made, why is in retained long after it would be useful, and why does it open in preference to the more recent database when clicking on the .cocatalog package?
After copying my database (.cocatalog package) from one drive to another, I clicked on the new copy of the .cocatalog package and the database opened from the new copy was over 200 hundred images short of the original and the recent import lists was for earlier dates ending well before the latest imports. It turns out that the package contained an old copy of the cocatalog.db database (with the word COPY inserted before the database name) along with the one that usually opens. When selecting the cocatalog package Capture One selected the copy of the database from the package instead of the latest version. As it happens, the database "COPY..." can be deleted forcing Capture One to open the most recent database.
I have referred this to C1 support with the following questions: What causes a copy to be made, why is in retained long after it would be useful, and why does it open in preference to the more recent database when clicking on the .cocatalog package?
0
Post is closed for comments.
Comments
0 comments