To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110686
------- Additional comments from moresoluti...@openoffice.org Tue May 18 10:17:07 +0000 2010 ------- I can confirm this also to be a problem (also with Citect). Looking at the binary data, the change seems to be that the (fixed length) records were previously padded with spaces, but are now padded with spaces with the exception of the last character in the record which is now null (0x00). My guess is that Citect interprets the NULL character as end-of-file (it does not complain about the file). Manually changing the end-of-record 0x00 to 0x20 with a hex editor makes the records visible to Citect. Note that I believe that Citect accesses DBF files through the Jet ODBC database drivers so this is probably not Citect specific. Citect users are just unusual in that they're using an application which makes heavy use of DBF files, but which does not provide very good editing tools itself, so it is common that the files are edited using tools like Excel or Calc. Calc 3.1 was fine. --------------------------------------------------------------------- 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...@sc.openoffice.org For additional commands, e-mail: issues-h...@sc.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
