>>As of now, it looks like data should be in a single table (like Excel) that internally contains several tables accessible through views. That requires the use of a DBC, I believe, although I am open to ideas. In any case, the framework we use (Codemine) requires a DBC that we can include in the project because it can be read only, but the data tables will be free tables. In order to keep it down to a single table we'll have to create indices each time we open. Too bad, but using a single table takes precedence.
>
>What would be the advantage of having a single table? It is much easier to manipulate information if it is properly normalized.

From the point of view of our user (a teacher out in the country) a single file seems to make more intuitive sense. (S)he could turn in the file to the office and say: here are the grades for my Algebra I group. It is only the programmers that have to be concerned that the file acually contains three (properly normalized) virtual tables. Thanks to Charlie Schreiner for the seed of this idea.