Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

Dan wrote:
Dan wrote:
Andreas Säger wrote:
Am 12.06.2012 21:08, Dan wrote:
To populate a list or combo box, I have been using single field tables. Seems like it should be possible to use a single table for more than one
list or combo box. (The SQL statement for selecting a field for a list
or combo box is: SELECT "field name" FROM "table name".) Has anyone
tried this before? Any problems doing this?


In a combo box you "always" want:

In a list box you "always" want:
SELECT "Field or Concatenation", "Primary Key"
FROM "Table"
ORDER BY "Field or Concatenation"
Bound field=1
Data field=The form's foreign key

[Example] Relations reflected by list boxes in forms
OK, I see I was not explicit enough. The tables I use for list boxes always contain only ONE field using VCHAR as the field type. There are no repetitions in this field, so all values entered are DISTINCT.
     The benefits I get from this are:

1) If I enter a new value in the field, close the table, and open it again; the entries have rearranged themselves alphabetically.

2) The entries always appear in alphabetically order in the list box after clicking the refresh tool in the form.

3) Field A has been replaced with a list box (i.e., Monday, Tuesday, Wednesday) in a form. (The table for this contains one field whose values are Monday, Tuesday, and Wednesday.) When field A appears in a report, the only values showing are Monday, Tuesday, and Wednesday. If I were to use a table having two fields: ID, Day (i.e., 1,2,3 for ID & Monday, Tuesday, Wednesday for Day); the form has shown the Monday, Tuesday, Wednesday values while the reports show 1, 2, 3. Obviously, more has to be included in the SQL than what I wrote in the beginning. But with the limiting structure of my tables for list boxes do not require anything more.


Perhaps an important point: The field used in the table for the list box is also the primary key. This guarantees that the field contains DISTINCT values.


For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.