The problem occurs when an alphanumeric column contains zeroes. The problem is NOT consistent and I have been unable to identify a consistent pattern. An alphanumeric (text or '@' pattern) value containing one or more zeroes will drop one of the zeroes. If there are multiple zeroes in the value, it is neither consistently the first nor the last. In a spreadsheet containing just fewer than 54,000 rows, each containing a unique 8-character value (the value in question), there were about 170 values that were not output properly: as stated, the incorrect values were missing a zero character. There were also several (quantity undetermined) that appeared to be completely similar in format but were output properly. The data set contains PII, so sharing example data must be handled carefully and properly.
Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 32; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.3 Calc: threaded
Please attach a sample file. And explain what you are trying to do step by step. e.g. opening a csv file, ..., save as dbf?
(In reply to Dick Hildreth from comment #0) > The data set contains PII, so sharing example data must be handled carefully > and properly. Sharing a file in bug reports means it is publicly available. https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission
(In reply to Dick Hildreth from comment #0) > In a spreadsheet containing just fewer than 54,000 rows I would suggest gathering a few values, some of them with the problematic pattern (containing double zeroes) and some values that don't comply with that pattern, instead of having 54000 rows. Then test such minimal file: use the appropriate cell format (as text) _before_ introducing the sample values, and saving the file as ods and then exporting it to dbf. I am guessing that such minimal files would not have confidential info (at lease not that other users could understand its meaning). If you can reproduce the problem in your own system with the minimal set of values, they should be enough for others to test. Please then attach each of those 2 minimal files, one at a time, using the "Add an attachment" link in the bug report page of this bug 156887 (please don't send the files as emails).
Dear Dick Hildreth, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Dick Hildreth, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp