In response to your questions:

1) On making it easier to enter track information on an album card: Track names and composers frequently tend to the complex. A number of compositions will appear on multiple albums. It should not be necessary to redundantly enter this information each time. In fact, this _must_ be avoided to maintain the integrity of the database. How frequently have you been on a single mailing list two or three times at once, each name or address just slightly different? This is what I want to avoid. But how do we make this "easy" in HyperCard? This is what I don't know.

2) It soulds like you have a good handle on the printing requirements: build up the label automatically as best as possible, then allow editing.

3) "We have been tossing around composers and performers as if they were equivalent..." My first reaction was to accuse YOU of mixing these two up, but I guess this is rather unfair. In fact, I had forgotten about the need for tracking performers on a lower than per-album basis on my early notes (the issue is that some albums are compilations, with perhaps each track being performed by a different group). So - slipping back to database terminology - we need a fourth table, PERFORMERS, and we need a pointer to this table from TRACKS.

Clear enough?

[Editor's note: I propose that we come back to this project in the Spring after the Conmtinent Generator and Pelago 2.0 are out of the gate.]