I had noticed that in the past. That's one that should get fixed. It's likely one line of code triggered when the dialog opens rather than when it's closed via clicking Ok. These little coding issues are a real pain to catch during testing. As a programmer I've made more than a few of these myself.

Probably most people learn how to avoid the error after they lose a bunch of work so it doesnt get a lot of attention. I'm guilty of that myself. I find a few little errors and never bother to report them because I work around them.

This state of affairs probably comes from the fact most software companies don't respond to bug reports anyway. PGM does and I should remember that and report any issues.

BiaB 2013 b366, RB 2013 b4, WinXP Pro SP3, Toshiba M70, 1.8GHz 2GB RAM 100GB HD. Focusrite Saffire 6 USB, Ketron SD2.BiaB Wiki