[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libreoffice-users] Form fields not filled

I using LibreOffice (version Base as client to a backend
Mariadb10 via MySQL(JDBC) connector.

I have a created a Query in Base of the form SELECT * FROM <tablename>
ORDER BY <Field1> ASC, <Field2> ASC

Why MUST these two sort fields be set to 'visible' in the query (thus
extending the above syntax accordingly), since they are any case part
of the source table? The columns appear twice in the opened query?

I have created a Form based on the above query. However, on filling out
the form for a new record and saving the data, a new record is created
in the table but the data of above two fields remain blank, i.e. are
NOT transferred to the source table. The two fields in the source table
remain blank, whereas all other fields are filled as expected.

Are these two aspects related? Should this be the behaviour? I would
not have expected the data from the two fields to be rejected.


To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-users] Re: Form fields not filledAlexander Thurgood <alex.thurgood@gmail.com>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.