You know, it would be wiser to aggregate the data even more. Rather than having the works table have fl_scored, cl_scored, etc, have a scored_id and another table that that links to.
scored id, instrument_id instruments id, name Sorry, did Oracle DBA for 2 years for a startup right out of college. Got to work with a genius of a guy who was the head database guy for Pacbell. On Tue, Aug 19, 2008 at 6:36 AM, shirling & neueweise < [EMAIL PROTECTED]> wrote: > > duh. obviously the contact info goes in the composer table. > > in the works table, for example: >> composition_title >> composed_in >> composer_ID >> fl_scored >> ob_scored >> cl_scored >> [...] >> fl_parts >> ob_parts >> cl_parts >> address >> city >> province >> country >> >> in the composer table: >> family_name (avoid using "last_name", can create coinfusion to people >> entering some names from aisia) >> given_name >> composer b. >> composer d. >> > > _______________________________________________ > Finale mailing list > Finale@shsu.edu > http://lists.shsu.edu/mailman/listinfo/finale > _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
