I agree with Bruce. Since you already know and love (?) ini files, and providing volumn of data you want to keep isn;t too huge, there's sure to be a way of handling your data as ini sections/keys.
If you have more than one book per year/month, you can go for: [yyyymmm] book1=xxx book2=yyy If you decide a database is needed, I might take back suggestion re using sqlite and propose using excel via odbc, assuming (a) it might be useful to see the whole dataset in one sheet without any additional work and (b) you're comfortable working with excel. he advantage of excel/odbc over sqlite is that you can enter the bulk of your data learning any scripting, just be adding to spreadsheet. Same goes for ini files, you can always stuff lots of entires in manually to start with, if that's a useful thing to do. --- In [email protected], "brucexs" <bswit...@...> wrote: > > --- In [email protected], "brother.gabriel" <brgabriel@> wrote: > > > > Well, I had not thought of a columnar text file; I was using ini out of > > instinct; but I need to pull data from individual fields without knowing > > their value. I suppose that could be done with vectors? I am good to go > > with ini files, but anything beyond that is going to be a learning curve. > Then go with ini. If you really just need to store the year month and an > assoicate value, then one format is > > [year] > 01=value > 02=value > > etc > ie use the year as the section, and the month as the key. > > It really depends on the exact data you want to process and how you want to > process it.
