No, this has been a problem for quite some time. The reason it does this is fairly complicated - is actually a bug in the part of Microsoft Visual Basic that handles printed reports. It can probably be programmed around, though. I'll ask Jon if its on his "to do" list.

V.

Vincent Meyer, MD
Meyer, Malin and Associates, PLLC