Revision history  [back]

This looks like an issue identified in DBv6.1 that has already been fixed (after DBv6.1.2.009).