Inability to save in version sets

[Bernard]

I'm new to Elements. Loaded it about 3 months ago and everything woorked fine for about 60 days. Then I lost my ability to save in version sets. Whenever I try to save to a version set now the image shows up in "watched files" then I've set it to autoload back to the Organizer and it shows up as a copy. Why can't I save in version sets anymore and what can I do to rectify the situation?

[Byron Gale]

Bernard,

I haven't a clue whether this will be helpful, or not... but it has been known to cure other "warts" in the Organizer.

Click File > Catalog... then click the Recover button and proceed with recovery. This grooms the MS Access database which is created by the PSE Organizer.

Again -- having not experienced what you report, I do not know whether this routine maintenance step will help you at all.

Byron

[SteveB]

I recently had the same problem, version sets were previously working but then mysteriously ceased to be saved after editing (using "save as" command). Exisiting version sets were ok. The database recover function as mentioned above did "repair" the database and now I can once again save version sets. Note that the files that previously failed to save in version sets will still be separate files (ie not in version sets).

[Byron Gale]

I recently experienced this same thing using PSE5.

Working through a large collection of images, I would routinely select the image, CTRL-I to open in Editor, and make changes. I would then close the image in Editor, opt to save the changes, and accept the suggested file name and location -- leaving the option to save in a version set selected, as offered by default in the dialog.

All would go as expected for a while, but I found that after doing this cycle on many successive images, suddenly an edited image would be saved, but the version set would not be created in Organizer. When it happened, I would Recover the catalog, and then close PSE Org and Editor entirely, and re-start again. A subsequent edit cycle would then create a second edited version, which would be added to Organizer in a version set, as expected. The first edited version still exists, but is orphaned.

Because I was working through a large number of images, and doing this edit cycle many times, I experienced the failure more than once. I estimate that I may have edited 50-60 images, and had 3 or 4 of these version set failures. There was not a predictable pattern to the number of cycles, or type of edits, leading up to a failure. Once the failure happens, all subsequent attempts to create version sets in this manner fail, until the steps described, above, act as a reset. It is almost as if the application gets "tired" and then begins to fail this way.

I don't know of a direct cause, but in my case the problem was always after doing several edit/save cycles in succession. NEVER in the first dozen, or so, images processed in a session.

This is no help, of course... I offer it as confirmation and documentation of the behavior.

[jazzfisher]

Byron,
Have had the same experience although not yet in 5.0--that's somewaht dismaying since there are times when I edit huge amount of photos (one after the other). I don't have a solution just smypathy.:(