sde, about making a midi recorder/player, that would definetely be the task after a search procedure was nailed down.
About creating a Relation Table, I'm not sure that that would be necessary, because any returned results are obviously related since they contain the same notes. Songs are not created by a single chord. Therefore, a user may search a chord, then another chord, and another, (all seperate querys), and then determine what scales and modes are common to all the chords by just looking at them. If you query "A B C#", I would like the exact match to be the first results, and "A B C# Db" to be the second results, and so on. The user may then have a better idea what scales to try over any given sequence of chord accompaniment.
Does this make sense, or do you have something else in mind that I'm not grasping. I'm not a music theorist, though indeed, this project is making me much more musically aware. I'm really just trying to match things to say, oh yeah, ok, maybe that scale would sound good with those chords, or...what is this chord I'm playing on my guitar, and where else on the fret board can I play this chord, or....oh, this chord is D Minor7 b5, where are all the minor7 b5's on my guitar, piano, violin, lets see what those would sound like. I liken a search chord/scale search engine to a search on the computer help file. It sure beats looking through the index of the printed manual for the topic I'm interested in. And, suprisingly, I have yet to find one on the internet! To me, it's so programmable, and so useful, that I'm simply compelled to do it. Plus, it's fun.
Forgive me for rambling
