I'm not messing with '06 until this is fixed. I'm back to '05 now. I haven't had time of late to keep up with this list as religiously as I do sometimes, so if there was any kicking and screaming about this situation (which there should have been) it got by me. If I'd known about this bug I'd never have switched to '06.
I talked to my copyist last night and since he wants to extract the parts for this work from one file he's going to reenter what's done so far (over 100 measures) into 2005. Basic bummer. For the record, the backup file that saved my bacon was the one that's updated every time the file saved, which is a separate backup file from the autosave file. As soon as I noticed the problem the first thing I *didn't* do was hit "command s", so as not to commit the problem to that file. I disabled autosave right away but didn't know for sure whether it had kicked in since the problem occurred. The autosave file was next on my list to check if I needed to do so. Now to badger MM. Don Hart on 10/18/05 4:00 AM, dc at [EMAIL PROTECTED] wrote: > Javier Ruiz écrit: >> Finale 2006 is unusable then... > > That's how I'd feel also. Who can take the risk of "losing everything", or > even your last five minutes of work, or whatever? If I were using 2006, I'd > go back to the "last stable version"... Especially considering the few new > interesting features in 2006. > > Dennis > > > > _______________________________________________ > Finale mailing list > [email protected] > http://lists.shsu.edu/mailman/listinfo/finale _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
