Data layer Organization

I am stuck in my app development. I am trying to develop simple numismatic app. This app should be built this way:

Countries DataTable -> SubCountries DataTable (example: Germany -> BRD -> DDR->...) -> SelectedCountryCurrencyList DataTable -> SelectedCountryCurrency -> SelectedCurrencyInfo View (It will contain 'add to my collection' button)

There's also the problem, that sometimes some countries are do not have any subcountries.

I am about storing the list of countries, subcou开发者_开发百科ntries and currencynames in plist. The full information about currency (including image) in SQL DB on remote server.

So, my question is how should I build the structure of my plist for this given situation. Should I store all of the stuff in one single plist file, or should I create more files?

Thank you in advance.

Another option is to use sqlite (with fmdb wrapper) or coredata. You could also pull down more of the currency information and images to the local store. That would make the relational queries faster, full currency and images faster and provide the benefit of full functionality on an occasionally connected device.