+2  A: 

NSArray's add: method is something you'd hook a button up to, when you have a Core Data entity that can be created and used without any initialization. In this case just call NSEntityDescription's

+ (id)insertNewObjectForEntityForName:(NSString *)entityName inManagedObjectContext:(NSManagedObjectContext *)context

with the managed object context you're using with your array controller and the appropriate entity name to create your managed object in code. You can set properties on it directly if you've created a subclass for your entity, or just use key value coding if you haven't done that yet.

Marc Charbonneau
Thanks for the help, but I'm still a little confused. See my edit.Thanks!
Walker Argendeli
Well, in your code you're creating an entirely new app controller, with either a second MO context or nil, and destroying it afterwards. This is a little backwards, since you already have an existing context to use.If I were in your shoes I would actually put Core Data on hold until you've had a chance to familiarize yourself with the Cocoa framework and the design patterns it uses. Core Data makes things easy in some respects, but it's not intended to replace the basics.
Marc Charbonneau
I know I'm probably in over my head, but I've been building an app based on Core Data, albeit with most Core Data things done in IB. I plan on familiarizing myself extensively with Core Data in the near future, but I'd like to get this one solved right now. Thanks for all your help, though.I think what I'm not sure of is how to access an entity from the model in the code, and how to access a specific instance of an entity in that code.
Walker Argendeli