I am doing some long overdue bundling. My process has been this: open a project, save as CWB, then delete the original (I have Sonar do this). That all works fine (most of the time), but when I open the next project to work on it, I get trouble. The project typically opens, and it may even begin to play if asked to, but Sonar goes into the (not responding) mess, then I have to close it. Once I restart Sonar, I can go right on to the next file and it works fine.
 
At what step have I caused this freeze-up to happen, if it's indeed my own fault?
 
I have also determined this will not happen if I do not delete between songs.

This is one for troubleshooting in the Sonar forums...

Then if someone can move it, please do so.

I notice that the Sonar documentation is now suggesting to use bundle files primarily (exclusively?) to transfer from one computer to another. It has always been deprecated as an archiving technique by many of the users. These forums have been rife with failed to open bundle files over the years. Other people have great faith in the format and have never had a problem. Saving projects to their own folder and then backing up those folders in their native format is the safest route. Compressing the project folder adds another level of risk. 
 
One potential problem with the bundle file is that it cannot be opened in safe mode. There was a recent post here where someone found that a bundle would not open at all, apparently because he did not have a plugin that was called in the bundled project. The same project saved in native format and opened in safe mode would have allowed him to bypass the troublesome non-plugin and get access to the project.

Bundles I am making today reopen easily. I'm still able to open bundles made before Sonar.
 
But why would Sonar freeze after deleting the original project?

My SONAR Platinum freezes when I try to open a cwb file.  Have to do a cntrl-alt-del to get out.  I have a previous recent thread on this.  Craig Anderton (and others) gave some good advice.
 
Good luck!

pencilartist
Bundles I am making today reopen easily. I'm still able to open bundles made before Sonar.
 
But why would Sonar freeze after deleting the original project?

That freezing is a mystery to me, but I would never trust only cwb-files in storing my projects. Then again, I have read many, many posts about freezing when exiting SONAR, but I can't recall ever seeing a clear answer to that issue.
 
The point is: If a bundle goes corrupt, your project is gone forever, if a cwp gets corrupt, you still have the audio
(if that's any comfort if your projects contain a lot of MIDI :o/)

When I create bundles, I test reopening them after creation. They get stored to DVD and tested again. You might assume I do know the horror of losing them forever. :)

Consider the scenario where your bundle contains a project with a call to a plugin that is not on the computer where you want to open it. And consider the not unheard of case, where that plugin is either a) no longer available anywhere in the version required, or B) you are no longer licensed to use it because your subscription has expired. The fact that you could open the bundle immediately after you saved it does not necessarily mean you will be able to open it in a couple of years. The bundle file is not a compressed format. You will save more space by zipping the project folder.

Considered, and lived. I have been at this for a number of years. I have opened bundles which are 10 years old, where numerous plugins are no longer present, and had no crashes or failures to open.
 
The matter of why Sonar crashes between deleting a project and opening a project is my issue. Not the wisdom of using CWB files.