To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87672
------- Additional comments from tomm...@openoffice.org Thu Jan 22 17:36:35 +0000 2009 ------- has any progress been done on this issue in the meantime? i suggested it as a 3.1 blocker but u think it didn't make the cut before the code freeze. what about 3.2? do you think there are chances to see it fixed for that release? please, understand my question are only led by curiosity... i'm not complaining at all about not having fixed yet my issue. i'm just wondering what kind of startegy are you thinking to use to prevent the data crash and overcome the 16-bit limitation --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
