Page 1 of 1

collection.crossdb

PostPosted: 18 Jan 2017, 04:01
by sudodj
Screen Shot 2017-01-17 at 8.55.05 PM.jpg


I'm using Cross 3.3.11, and my Mac's battery died. When I started up again, I got this message. It won't read the database, and wants to write a new DB file (which of course is then empty). Any ideas? Is this recoverable?

Re: collection.crossdb

PostPosted: 18 Jan 2017, 04:18
by daniel clark
:neutral: by chance have you created other collections ,, ie from earlier versions ,, there is a tab for loading collections ,if there was more than one then this is where it will be ,, :cool:

Re: collection.crossdb

PostPosted: 18 Jan 2017, 11:02
by RoJeC
You should start with making a backup of this file together with the file with the same db name with extension .journal.

The normal database process (approximately) is that any changes you make while the db is open are marked in the database and are written in the journal. Once you close Cross (or change collection) the journal is applied to the database file, making all changes permanent.

Your battery like died at a moment or the shut downproces caused the files to become out of sync.

WHile you have your backup safe you can try the following:
1. verify the file attributes to make sure there isn't a simple 'in use' state of the files.
If so, change and start Cross to see if this was it.

Else
2. copy the files to a new name (just to avoid using the backup file)
delete the original .journal
start Cross
If this works you'll see you have the database back to the state before the start of your error session.

If this doesn't work, send your backup (2 files) to support@mixvibes.com and maybe they can fix it for you.

Important lesson: don't forget to occassionaly backup you collection, so you max loose a limited period of effort...

Re: collection.crossdb

PostPosted: 19 Jan 2017, 03:22
by sudodj
Thanks Ronald, gave it a try and unfortunately no luck. I'll email them in and hopefully someone can give me a hand.

Adam

Re: collection.crossdb

PostPosted: 19 Jan 2017, 23:50
by discopex
Where did the original database file go or are there any additional ones?