Thanks for responses guys. Actually what I was wanting to do was share MIDI melody data, not chords. Chords are a piece of cake. Melody is quite a bit more complicated. See, here's a more complete explanation.

Occasionally I'll use the Melodist utility to generate a melody. Most of the time it's pretty forgettable stuff, but every once in a while the Melodist will hit on something that I'll consider a keeper. So what I'll do is have the Melodist generate several melodies and then I find that I might have a few clips worth adding to the melody. Now, I could just print out what the Melodist has generated and then enter the notation myself, and while it would be rather tedious, at least it would work. But here's the kicker -- the Melodist is actually pretty slick when it generates melodies. There's a lot of quantization going on and also quite a bit of variation in volume, all in a bid to make the melody sound "natural." Duplicating this level of quantization means I would have to right click on every single note and type in the data from the Melodist's generated notes. That suddenly becomes an ordeal I'd just as soon live without.

BUT!!!! Pipeline's mentioning copying stuff to the Notepad gave me an idea. What if I copied notation data just doing a CTL-C, then clicking on the popup BiaB generates, exit that file, load the target file, locate the cursor where I want to insert the notes, then do a CTL-V. And guess what? It worked! So, I dunno if the BiaB folks are even aware of this, but it turns out that this is a function that can be accomplished by just doing a simple copy to the Notepad.

Actually, turns out it is a little more involved than that. I found I had to clear the area in the target file where I wanted to insert the new note data first. If there are any notes in the target area, they can't be there cuz trying to get rid of them using the Cut or CTL-X command dumps the saved notes from the Notepad. Not really a big deal, cuz it's something I'd need to do anyway.

Made my day. What a relief!