First time here? Check out the Help page!
answered 2020-09-22 11:02:10 -0600
This looks like an issue identified in DBv6.1 that has already been fixed (after DBv6.1.2.009).