Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Persistent column widths: tables, views, queries, & form table controls

Persistent column widths?

  • Of the four types of tabular data in Base, is the Query the only one that doesn't have persistent column widths?

  • Is there a way to make the column widths of a Query persistent (remembered from session to session), or am I doing something wrong?

  • Does any of this depend on the particular database one is using or connecting to?

In other words, when I open a Table, I can adjust a column width manually, either by dragging left or right, or by double clicking on the line between two columns. And when I close the Table and then re-open it later the column width is remembered. The same seems true in Views and in Form Table Controls.

But this does not appear to work in a Query. Each time I run a Query to view the data, it forgets the previous column widths and sets new unhelpful column widths.

Currently using LO 5.2 & Connecting to MariaDB.

Persistent column widths: tables, views, queries, & form table controls

Persistent column widths?

  • Of the four types of tabular data in Base, is the Query the only one that doesn't have persistent column widths?

  • I also noticed that a View's column widths are forgotten from LO session to session.

  • Is there a way to make the column widths of a View and Query persistent (remembered from session to session), or am I doing something wrong?

  • Does any of this depend on the particular database one is using or connecting to?

In other words, when I open a Table, I can adjust a column width manually, either by dragging left or right, or by double clicking on the line between two columns. And when I close the Table and then re-open it later the column width is remembered. The same seems true in Views and in Form Table Controls.

But this does not appear to work in a Query. Each time I run a Query to view the data, it forgets the previous column widths and sets new unhelpful column widths.

Currently using LO 5.2 & Connecting to MariaDB.

Persistent column widths: tables, views, queries, & form table controls

Persistent column widths?

  • Of the four types of tabular data in Base, is the Query the only one that doesn't have persistent column widths?

  • I also noticed that a View's column widths are sometimes forgotten from LO session to session.

  • Is there a way to make the column widths of a View and Query persistent (remembered from session to session), or am I doing something wrong?

  • Does any of this depend on the particular database one is using or connecting to?

In other words, when I open a Table, I can adjust a column width manually, either by dragging left or right, or by double clicking on the line between two columns. And when I close the Table and then re-open it later the column width is remembered. The same seems true in Views and in Form Table Controls.

But this does not appear to work in a Query. Each time I run a Query to view the data, it forgets the previous column widths and sets new unhelpful column widths.

Currently using LO 5.2 & Connecting to MariaDB.

Persistent column widths: tables, views, queries, & form table controls

Persistent column widths?

  • Of the four types of tabular data in Base, is the Query the only one that doesn't have persistent column widths?

  • I widths? (I also noticed that a View's column widths are sometimes forgotten from LO session to session.session, but they seem to be retained always so long as you don't restart LO.)

  • Is there a way to make the column widths of a Query and View and Query persistent (remembered (i.e. remembered from session to session), or am I doing something wrong?

  • Does any of this depend on the particular database one is using or connecting to?

In other words, when I open a Table, I can adjust a column width manually, either by dragging left or right, or by double clicking on the line between two columns. And when I close the Table and then re-open it later the column width is remembered. The same seems true in Views and in Form Table Controls.

But this does not appear to work in a Query. Each time I run a Query to view the data, it forgets the previous column widths and sets new unhelpful column widths.

Currently using LO 5.2 & Connecting to MariaDB.

Note, that when connecting, the View is in the connected to DB, not in LO. You can create a View by first creating a query, then saving it as a View. You won't be able to edit it again in design mode! It's now designed in SQL on the MariaDB server.

The design cycle is awkward: Create a query. Create a View. Set column widths. Change the query. Again create a View. Setup all of your column widths all over again.

Persistent column widths: tables, views, queries, & form table controls

Persistent column widths?

  • Of the four types of tabular data in Base, is the Query the only one that doesn't have persistent column widths? (I also noticed that a View's column widths are sometimes forgotten from LO session to session, but they seem to be retained always so long as you don't restart LO.)

  • Is there a way to make the column widths of a Query and View persistent (i.e. remembered from session to session), or am I doing something wrong?

  • Does any of this depend on the particular database one is using or connecting to?

In other words, when I open a Table, I can adjust a column width manually, either by dragging left or right, or by double clicking on the line between two columns. And when I close the Table and then re-open it later the column width is remembered. The same seems true in Views and in Form Table Controls.

But this does not appear to work in a Query. Each time I run a Query to view the data, it forgets the previous column widths and sets new unhelpful column widths.

Currently using LO 5.2 & Connecting to MariaDB.

Note, that when connecting, the connecting (i.e. not using the Embedded HSQLDB data base), the actualy View setup is in the connected to DB, DB (in my case in MariaDB), not in LO. (I image this is faster.) You can create a View by first creating a query, then saving it as a View. BUT! You won't be able to edit it again in design mode! mode. It's now designed in SQL on within the MariaDB server.

To edit it you need to directly edit it's SQL. (Possibly you can copy it's SQL into a query's SQL, then switch to design mode.)

The design cycle is awkward: awkward: Create a query. Create a View. Set column widths. Change the query. Again create a View. Setup all of your column widths all over again.

Persistent column widths: tables, views, queries, & form table controls

Persistent column widths?

  • Of the four types of tabular data in Base, is the Query the only one that doesn't have persistent column widths? (I also noticed that a View's column widths are sometimes forgotten from LO session to session, but they seem to be retained always so long as you don't restart LO.)

  • Is there a way to make the column widths of a Query and View persistent (i.e. remembered from session to session), or am I doing something wrong?

  • Does any of this depend on the particular database one is using or connecting to?

In other words, when I open a Table, I can adjust a column width manually, either by dragging left or right, or by double clicking on the line between two columns. And when I close the Table and then re-open it later the column width is remembered. The same seems true in Views and in Form Table Controls.

But this does not appear to work in a Query. Each time I run a Query to view the data, it forgets the previous column widths and sets new unhelpful column widths.

Currently using LO 5.2 & Connecting to MariaDB.

Note, that when connecting "connecting" to a data base, (i.e. not using the Embedded HSQLDB data base), the actualy base), the actually View setup is in inside the connected to DB (in my case in MariaDB), not in LO. (I image I imagine this is faster.) faster.

You can create a View by first creating a query, then saving it. Then right clicking on it and selecting Create as a View. BUT! View. BUT! You won't be able to edit it again in design mode. It's now designed in SQL within the MariaDB server. To edit it you need to directly edit it's SQL. (Possibly you can copy it's SQL into a query's SQL, then switch to design mode.)mode. I tried this and am still working the bugs out of this approach. It works for simple, but not more complex queries.)

The Gripe: So the design cycle is awkward: 1) Create a query. 2) Create a View. 3) Set column widths. 1a) Change the query. 1b) Again create a View. 1c) Setup all of your column widths all over again.again! What a pain.