Hello,
I think this one is probably a bug in the backup() mechanism. So I
suspect the backup is just dumping what is current into the backup
directory. But that directory is never cleared out of old stuff.
Unfortunately that can lead to the kind of key error you have seen.
When it starts up, the program tries to load all the data in the project
directory (well, including sub-directories) and so if there is an old file
lying around with a duplicate key to the current file then it will
complain when loading (it might even load the old file first, there is no
telling). In this case the old file must be in
PROJECT_backup/ccpnmr/NameMapping
so check in there for the timestamp of the *.xml files. There are likely
only a couple of files and most likely only the most recent should be
kept. (But backup everything before starting to delete anything!)
Wayne
On Tue, 5 Feb 2013, T J Carruthers wrote:
> Oh - and I don't know if it is related, but:
>
> when I try and save the project under a different name (as a precaution now!) I
> often get the following error box pop up:
>
> Save project
> Cannot add child - dey already in use:
> ccpnmr.NameMapping.NameMappingStore:<memops.Implementation.MemopsRoot
> id:4455666192>:IMP1
> <OK>
>
> (uh - I think I must have mistyped and now I can't get the error to happen again -
> I don't think it said "...dey already...")
>
> (it was called IMP1 originally, now it is IMP1_5 and I was trying to save it as
> IMP1_6 this time)
>
> I click the OK button, and then try to save again with the same name I tried the
> first time, then it saves successfully!
>
> Project saved
> Project saved successfully
> <OK>
>
> I then close the save as window, and try to save as again with a new name and
> there error doesn't occur.
>
|