Thank you! That is what I have been hinting at.
David W. Fenton wrote:
The key distinction between data stored in a spreadsheet and data stored in a relational database is that the latter separates data storage from data presentation, whereas in a spreadsheet, the place where you store the data is the same place used for printing -- there is no separation between data layout and print layout in a spreadsheet (though that's not entirely true -- certain kinds of features do allow multiple presentations of the same data from one worksheet).
In a relational database, the data is stored in objects that are designed to represent the characteristics of the data itself, with no concern for printout or presentation. In a relational database, a report can be used to draw data from multiple related data tables and present it in any number of different ways, each specific to the purpose of the individual report, hiding certain things, revealing certain others.
For example:
http://www.bway.net/~dfassoc/Park/Reports.html
There are a couple dozen reports, presenting data mostly from a handful of data tables. In a spreadsheet, each of those reports would require its own spreadsheet page (or, perhaps, in the case of closely related reports, editing of a single spreadsheet page to produce two slighly different printouts), but in a relational database, the report layout is defined entirely separately from the data, allowing an infinite number of presentations, without requiring re-arrangement of the underlying data.
A score printout and a part printout ought to be defined at the same level, as something cosmetic that is independent of the underlying music represented in it. Then you could have as many different presentations as you wanted, and changes to the music would flow through into all the various printed versions.
_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
