https://bugs.documentfoundation.org/show_bug.cgi?id=132780
--- Comment #35 from Pedro <[email protected]> --- There's so many differences than it's not even funny. We can start with name: Database range is meaningless to the common user. One can't even fathom it is supposed to be a similar functionality (hence why it was placed in Data tab in Tabbed UI instead of Insert tab. In Excel, Table is in Insert tab). Scope there: 1 - Change name of "Define Range" uno command to Table. 2 - Move command from Data Tab to Insert tab in Tabbed UI. Moving on. When one defines a table in Excel, it provides a Table design with a Table Style. Database Range has nothing. It has a handle to drag the Table to the neighbor columns and rows. Database range has nothing visible. Scope: 1 - Implement a table style upon creation of a database range. 2 - Implement a handle to expand table size. When selecting the Range in Calc in a completely different command (hidden in a menu) it is possible to expand the range of the table. However, it does not propagate the table style. It fills the new cells with new values based on expanded table. When creating a Table in Excel, a new tab in the UI is created (Table Design) with multiple options to change the design of the table (Header Row, First Column, Last Column, Banded Rows, Total Row, Last Column, Banded Columns). Nothing in Database Range. Scope: Table Styles. Any type of table styles. AutoFormat table styles should be implemented to Selected Range. It should be possible to better configure AutoFormat styles. There's the option to export the table data to Sharepoint list. There's a Tools group with: 1 - Remove Duplicates, 2 - Insert Slicer, 3 - Convert to Range 4 - Summarize with PivotTable. There's nothing in the comparable function of Calc. Scope: Add all these. The scope is enormous: new UI, new functions. If no one wants -- You are receiving this mail because: You are the assignee for the bug.
