>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.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
