Bob, maybe let us know what version of SB3 you're running.

If you're current, it might be worth asking support about that bug, I haven't seen it specifically listed as fixed in the release notes.