Member
2011-03-18, 12:08 PM
I agree that this looks pretty broken! I haven't had a chance to try to take a brand-new database and cause this behavior (it does occur with my data), but it is disappointing that this change was apparently made just before release and none of the testers spotted the problem.