Yes, to your last question. But the problem is, when I do the right-click/edit thing, what shows up in the box is an F#, not a Gb. So the program is telling me it knows what's supposed to be shown, but another part of the program is insisting that a Gb is used. Internally inconsistent. And somewhere there is an obvious bias toward flats as opposed to sharps. Being a guitarist, I am predisposed to seeing key signatures with sharps, but only rarely ones with flats. Reason is, with one flat I've lost one open string. With two flats, I've lost three, including both E strings. With three flats, I lose another open string. Whereas with sharps, one sharp no open strings are affected. With two sharps, no open strings are affected. With three sharps, one open string is affected. Compare that to three flats, where I've lost four.

As for your first comment, yes, this is what I was trying to explain -- that the second G, according to music notation rules, MUST be a Gb, since it's not showing an accidental symbol. But when you do the right-click/edit thing, what appears in the little box is a G#, and that is the note that is sounded. So if the Gb would be shown as an F#, then just showing a plain G without accidentals is correct for the key of A.

So, once again, all that is needed to clean up this bit of untidiness is for the F# to be displayed (and recognized), and everything will be copacetic.

Like I wrote above, I suspect this is just a quirk with BiaB that I'm gonna have to live with. Maybe v2019 will take care of this bit of oddity.

Best,
Michael

My Music:
https://soundcloud.com/michaelmcbroom/albums