If I were to do something like this I'd forget about trying to work directly with the spreadsheets. I'd look at the data in them, designed a database schema, imported data from the files into a database and computed whatever I needed using SQL. The point is that even though you may have a fairly well defined task now, it's almost inevitable that sooner rather than later you will need to compute something different. And then it will be nice to already have the data in an easy to work with format.
As a design exercise, if you decide you are not going to use a database, it's IMHO best if you do it the best you can, learn from your mistakes, refactor the code, see what was hard to change and what was easy, learn from your mistakes, redesign the program from scratch, write new code, see where was it better or worse than the original design, ...
Jenda
Enoch was right!
Enjoy the last years of Rome.
In reply to Re: Design elegance : How to best design this simple program ?
by Jenda
in thread Design elegance : How to best design this simple program ?
by mascip
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |