Memory Management is powerful

One wrong release can send your entire app to the graveyard. I'll explain why;

In a lot of areas of my program I invoke the use of class methods. Class methods are different from instance methods in that they are not applied to an instance of a class but to the class itself.

If you invoke class methods on your own custom classes, an instance of the class is required. However this is not the case with Foundation classes, don't ask me why.

Now when a Foundation class method is called you do NOT release that class afterwards, doing so will result in a crash of epic proportions.

I have now learnt this lesson for the umpteenth time and have implemented the save and load features successfully.

While testing the application, a local copy needs to be maintained on the test machine to ensure file creation functions correctly. I will need to load local versions of the project on beta testing machines.