Hello all together,
in Access you can use a „Nachschlageliste“ (in English look up list, I
guess). It is a sort of list box control, which is used for a field,
which contains a foreign key. You can set it to multiple columns and so
it shows the whole record, which is referenced.
In OOo the feature for multiple column controls is still in state “spec
draft”
(http://dba.openoffice.org/specifications/forms/multi_column_list_controls.odt).
So I look for a workaround.
I have got the idea to connect all the columns I want to see and make
this the first column of a query and the primary key of the referenced
table the second column in the query. You can see it in
KurssystemBeispiel.odb, the example which I used before. I have updated
http://www.rhenschel.homepage.t-online.de/KurssystemBeispiel.odb
(1)
I notice that the parser do not allow constant strings.
SELECT "KdID" + ': ' + "Vorname" + ' ' + "Name" + ' ' + "Geburtsdatum"
AS "gesamtname", "KdID" FROM ...
do not work because of syntax error. But
SELECT "KdID" + CHAR( 58 ) + SPACE( 1 ) + "Vorname" + SPACE( 1 ) +
"Name" + SPACE( 1 ) + "Geburtsdatum" AS "gesamtname", "KdID" FROM
"Teilnehmer" "Teilnehmer"
works.
In native mode the first query works without problem, see query
“fullname_native_constant”.
(2)
With the second version I create a query in parsed mode
“Fullname_parsed” and one in SQL native mode “Fullname_native”. The
result tables look same to me. But if I use this queries in a listbox
(set type to query and select the query for content) the query in native
mode shows the concatenated values as expected but with the query in
parsed mode I only see the first part of the string. The same occurs, if
you do not use a query, but write the SQL statement directly into the
list box properties.
Do I miss something, bug or not implemented?
kind regards
Regina
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
