[Upstream] Data copied from Base Table to Calc spreadsheet is wrongly formatted

Bug #1032094 reported by Tony Pursell
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LibreOffice
Invalid
Medium
libreoffice (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

What I expected to happen:

The table in Base contains 126 columns. If correctly formatted the 126 data items take up one column each, i.e. columns A to DV. Each cell should have Default formatting.

What happened instead:

When copied and pasted into a Calc spreadsheet, the first 35 data items span 3 columns each, taking up the first 105 spreadsheet columns from A to DA. Then from columns DB to DU there are a further 10 data items spanning 2 columns each. The other 81 data items are correctly allocated 1 column each, taking columns DV to GX.

This problem seems to relate to the number of columns copied and pasted. A table with only a few columns has data items correctly allocated 1 column each.

There is also other mis-formatting with strikethrough and underline formatting being applied to the data items. (This can be corrected using Format > Cells and setting '(Without)' for Strikethrough and Underlining on the Font Effects
in place of the blank entries found.) This mis-formatting occurs with any size table.

This has been added to a similar upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=51918

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libreoffice 1:3.5.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
Uname: Linux 3.2.0-29-generic-pae i686
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
Date: Thu Aug 2 09:32:28 2012
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to precise on 2012-04-29 (94 days ago)

Revision history for this message
In , Benjamin-lichtner (benjamin-lichtner) wrote :

Problem description:

After reading how to export data from Base (http://help.libreoffice.org/Common/Importing_and_Exporting_Data_in_Base), I attempted to follow the steps to export a csv. I copied the data from a table in my database and pasted it into a new spreadsheet, but the header row was completely alphabetized (and thus misaligned), and each header name occupied more than a single column.

Steps to reproduce:
1. Import an mdb or accdb file into Base
2. Open a table
3. Copy the table
4. Open a new spreadsheet
5. Paste into the spreadsheet

Current behavior:
Elements of the header row are alphabetized and occupy more than one column. Thus they are not properly aligned with each column of data.

Expected behavior:
Each element of the header row is properly aligned with the corresponding data column.

Platform (if different from the browser):
Windows 7

Revision history for this message
In , Nv4y-robert (nv4y-robert) wrote :

I can't reproduce it. Have no mdb- or accdb-file. Could you please declare it with an attachment (*.odb-file and screenshot of *.odt-file)?

Revision history for this message
In , Benjamin-lichtner (benjamin-lichtner) wrote :

Sure. Here's a link to a dropbox folder containing an .odb file, the .accdb
file to which it is linked, and the .ods file into which I pasted one of
the tables.

https://www.dropbox.com/sh/psavwxluly5awpj/Wh_2egYE76

--Benny

On Fri, Jul 13, 2012 at 11:26 PM, <email address hidden> wrote:

> https://bugs.freedesktop.org/show_bug.cgi?id=51918
>
> <email address hidden> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> CC| |
> <email address hidden>
>
> --
> Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

Revision history for this message
In , Nv4y-robert (nv4y-robert) wrote :

The *.odb-file is linked to a database outside the file. I couldn't see any table. I could not open an accdb-file - have no Access here and no Windows.
I can not see which sorting the headers of the table had, before they are imported.
When I take a table from a *.odb-file and paste it to a *.odt-file, the sorting is correct.
You didn't import the Access-file in *.odb. How do you connect the *.odb-file to the accdb-file?
The header of this bug is misleading. You havn't a Base-table. You have only a look on a table of another database. When you write about Base-table, we would search for the bug only in a *.odb-file, not a linked file to another database. The database of the *.odb-file is HSQLDB.
The problem must be the connection between the accdb-file and LO. There is no possibility to connect to an accdb-file with a standard-LO-installation.

Revision history for this message
In , Benjamin-lichtner (benjamin-lichtner) wrote :

Hi. To create the .odb file that I sent you, all I did was create a new
Base file, select connect to an existing database, select Microsoft 2007,
and select the .accdb file. However, I did need to boot into Windows--the
connection is not possible on OS X. Is there a way to save a new .odb file
after connecting it to another database? Or any other way to make the new
.odb file independent of the .accdb file? I apologize for the misleading
title. I am not familiar with databases.

On Sat, Jul 14, 2012 at 8:58 AM, <email address hidden> wrote:

> https://bugs.freedesktop.org/show_bug.cgi?id=51918
>
> --- Comment #3 from <email address hidden> 2012-07-14 06:58:31 UTC ---
> The *.odb-file is linked to a database outside the file. I couldn't see any
> table. I could not open an accdb-file - have no Access here and no Windows.
> I can not see which sorting the headers of the table had, before they are
> imported.
> When I take a table from a *.odb-file and paste it to a *.odt-file, the
> sorting
> is correct.
> You didn't import the Access-file in *.odb. How do you connect the
> *.odb-file
> to the accdb-file?
> The header of this bug is misleading. You havn't a Base-table. You have
> only a
> look on a table of another database. When you write about Base-table, we
> would
> search for the bug only in a *.odb-file, not a linked file to another
> database.
> The database of the *.odb-file is HSQLDB.
> The problem must be the connection between the accdb-file and LO. There is
> no
> possibility to connect to an accdb-file with a standard-LO-installation.
>
> --
> Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

Revision history for this message
In , Nv4y-robert (nv4y-robert) wrote :

Could be the same way I can import the thunderbird-adressbook, when I want to edit the files:
Open the database with the connection to the *.accdb-file. Create another new database. Click with the right button of the mouse on the table of the old database: copy. Click with the right button on the new database in the folder tables: paste. You are asked something about the types of the fiels. You can also sort the fields. Normally the fields are sorted as in the table of the old database. Try the automatic way. Could be you are asked for a primary-key. There was a key in the *.accdb-file. When you will use the new database not only for testing you must have a primary-key. If you don't know what it is you could also accept, that base creates a new key.
The table would be created by this wizard. Are the fields sorted as they are sorted in the table of the old database?
Now you could import the content in different ways to calc. They must be sorted like they are sorted in the new created database.
After this we will see, which is the right title of this bug and we could say, this is a bug for Windows, not for Linux or Mac (because there is no easy possibility to connect to *.accdb-files).

Revision history for this message
In , Tony Pursell (ajpursell) wrote :

I have seen a similar problem copying from Base to Calc.

The table in Base contains 126 columns. When copied and pasted into a Calc spreadsheet, the first 35 data items span 3 columns each, taking up the first 105 spreadsheet columns from A to DA. Then from columns DB to DU there are a further 10 data items spanning 2 columns each. The other 81 data items are correctly allocated 1 column each, taking columns DV to GX.

If correctly allocated the 126 data items take up columns A to DV.

This problem seems to relate to the number of columns copied and pasted. A table with only a few columns has data items correctly allocated 1 column each.

There is also other mis-formatting with strikethrough and underline formatting being applied to the data items. This can be corrected using Format > Cells and setting '(Without)' for Strikethrough and Underlining on the Font Effects in place of the blank entries found. This mis-formatting occurs with any size table.

I am using LO version 3.5.4.2 in Ubuntu 12.04LTS

Revision history for this message
Tony Pursell (ajpursell) wrote :
penalvch (penalvch)
summary: - Data copied from Base Table to Calc spreadsheet is wrongly formatted
+ [Upstream] Data copied from Base Table to Calc spreadsheet is wrongly
+ formatted
Revision history for this message
In , Tony Pursell (ajpursell) wrote :

@benjamin_lichtner

Rather than connecting a Base (odb) file to an Access database, can you export the table to CSV (you used to be able to do do this in the days when I worked with Access mdb files) then copy that into a table in an odb file, then try copying back to Calc?

If this still causes the problem that you observe, then it is not the connection to the Access database that is the problem, but the copy from Base to Calc (as I have observed. You will then have a the odb file that you can attach here as a test case.

Tony

Changed in df-libreoffice:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
In , M-dr-s (m-dr-s) wrote :

Hi reporter,

it is necessary to make the bugreport reproducible. Please do following:
1) Ceck if object/title of this bugreport is correct
2) List the single steps in details to reproduce your procedure
3) attach database-file and screenshot(s)

Revision history for this message
In , Tony Pursell (ajpursell) wrote :

Created attachment 66342
Database (odb) file

Revision history for this message
In , Tony Pursell (ajpursell) wrote :

Created attachment 66343
Calc file showing formatting problems

Revision history for this message
In , Tony Pursell (ajpursell) wrote :

Created attachment 66344
Screen shot of the Format Cells dialogue

Revision history for this message
In , Tony Pursell (ajpursell) wrote :

Hi Jochen

I am not the original reporter (<email address hidden>). I have added myself to this bug as my problems are the same or similar. Please let me know if you would prefer me to create a separate bug report.

This bug was originally reported at https://bugs.launchpad.net/df-libreoffice/+bug/1032094 See that for further details.

I have uploaded three files

i) A database file LS.odb containing a table Test2
ii) A Calc file copyout2.ods which shows the formatting problems
iii) A screen shot ScreenshotOfFormatCells.png

The file copyout2.ods was created by:-

1) Opening a new Calc document
2) Opening the file LS.odb
3) Selecting Tables
4) Right clicking on Test2 and selecting Copy
5) Switching to the Calc document
6) Copying data with Ctrl-V (cell A1 should be selected)
7) Saving the Calc document as copyout2.ods

Please let me know if you need any more information

Tony

Revision history for this message
In , Benjamin-lichtner (benjamin-lichtner) wrote :

Thanks for taking this on, Tony!

Changed in df-libreoffice:
status: New → Incomplete
Changed in df-libreoffice:
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :
  • LS.odb Edit (438.7 KiB, application/vnd.oasis.opendocument.database)
Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libreoffice (Ubuntu):
status: New → Confirmed
Revision history for this message
In , Iplaw67 (iplaw67) wrote :

Adding self to CC if not already on

Revision history for this message
In , Tony Pursell (ajpursell) wrote :

I have retested thus using LO version 4.2.7.2 and Ubuntu 14.04 and it seems to be OK now so I am changing the status to RESOLVED/FIXED.

If any one else still has this problem using 4.2.7.2 or later, please put it back to NEW.

Revision history for this message
In , Adolfo Jayme Barrientos (fitojb) wrote :

(We reserve the FIXED resolution when we know the exact commit that fixed a bug. When a bug becomes obsolete or is not reproducible anymore, we set the WORKSFORME status.)

Changed in df-libreoffice:
status: Confirmed → Invalid
Revision history for this message
Rolf Leggewie (r0lf) wrote :

closing here, too

Changed in libreoffice (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.