I must apologize for not responding to the replies to my original
problem back in October, 2007. I think I am on the right track now.
First, I must say that I am not an SQL guru. My background is in
computer hardware-software interfaces and embedded systems programming
in C and assembly. I am slightly familiar with SQL from experiences,
but no where near proficient in it.
I need to thank Juraj Trenkler, Drew Jensen, and Frank Schönheit for
their help in pointing me in the right direction toward resolution of my
problem with OO.o Base.
I was able to get something going from Juraj's suggestion of 6 October
07 and I have been experimenting with it. As a result, I have some data
that may help to improve OO.o Base.
1. I have looked at what Rekall generates as a listbox SQL query and
this is what they generate for my "Suppliers" list box, which is what I
am trying to recreate in Base:
SELECT SupplierID, Name, Address, City, State, SupplierID
FROM suppliers ORDER BY Name, State, City, Address
My "suppliers" table contains a list of suppliers and their addresses,
etc. I use the index (SupplierID) into this table from many other
tables, reports and forms.
2. I tried this query in Base's List Box Properties - List Content box,
to no avail. I did not get an error, but all I got was the first
column, the SupplierID field.
3. I then tried Juraj's suggestion of using CONCAT and that did work.
However, as Drew has stated in his response also of 6 October 2007,
everything was concatenated together and virtually unreadable.
4. Looking in my MySQL manual, I discovered the CONCAT_WS function,
which is supposed to insert a specified delimiter string between each
field. However, Base objected, stating that it was an unrecognized
field. I tried `,` , `-` and even `|`, but I got the same error no
matter what I used as a delimiter string. I must assume Base does not
support the CONCAT_WS function and its query testing fails the delimiter
field (1st argument to the function).
5. I then tried Drew's suggestion of nested CONCAT functions. This
also does not work. I get a similar failure as in the CONCAT_WS
function. Base complains about the use of ` ` as the first field of
the CONCAT function.
6. As an observation, I also noticed many random blank records in the
list box. I am not sure this is a Base effect or a MySQL response. It
is not a problem for me, it is just not very clean and "pretty".
7. The "ORDER BY" in the query does seem to work in Base. The records
are displayed in the ordering specified.
I would like to know how to get the CONCAT_WS function or, as a
alternate option, the nested CONCAT functions workaround working with
strings that are not field names of the table. If I can get that to
work, even if not very pretty yet, then I may be able to use Base.
Thanks again to all who have responded to my problem and pointed me in
the right direction.
Girvin Herr
Hello Girvin,
Now that version 2.4.1 has been released, I have looked at the fix list
and do not see any reference to the resolution of my problem of last
October (copy below). I have not received a reply to my posting
either. I just tested the 2.4.1 version and I verified that the list
box creation wizard still does not support multi-column list boxes.
What is the status of this issue?
The lack of this feature is still preventing me from using
OpenOffice.org Base.
Seems you missed the responses last time (they were probably all sent to
the list only, not to you personally) - they're all still valid:
http://dba.openoffice.org/servlets/BrowseList?list=users&by=thread&from=1873838
Ciao
Frank
--
- Frank Schönheit, Software Engineer [EMAIL PROTECTED] -
- Sun Microsystems http://www.sun.com/staroffice -
- OpenOffice.org Base http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Now that version 2.4.1 has been released, I have looked at the fix list
and do not see any reference to the resolution of my problem of last
October (copy below). I have not received a reply to my posting
either. I just tested the 2.4.1 version and I verified that the list
box creation wizard still does not support multi-column list boxes.
What is the status of this issue?
The lack of this feature is still preventing me from using
OpenOffice.org Base.
Girvin Herr
-------- Original Message --------
Subject: Multiple Columns in Base List Boxes
Date: Thu, 04 Oct 2007 14:08:10 -0700
From: Girvin R. Herr <[EMAIL PROTECTED]>
To: [email protected]
I was told by the users forum moderator to send the following to this
forum instead. So, here goes:
----------------------
I am running Linux OpenOffice.org 2.3.0 and despite previous failures, I
finally got Base talking to my MySQL 5.0.24a server. That part works
fine. I have been using Rekall 2.4.5 for a few years but its development
seems to be stagnating and so I have been looking at OpenOffice.org Base
as an alternate or replacement database client. As a test, I have been
recreating one of my forms for data entry in Base and discovered that
Base has many of the features that I like.
However, I have run into a "work-stopper" problem that may just prevent
me from using Base. This problem is the lack of support for multiple
columns displayed in a List Box in a form. I have spent a lot of time
researching this problem and I have come to the conclusion that this
feature is still missing in Base. In my research, I found a draft
document on OpenOffice's website dated 2005-06-01 written by a Frank
Schonheit, Document ID: SPEC.DBA.MCLIST (
http://dba.openoffice.org/specifications/forms/multi_column_list_controls.odt
), that addresses this feature deficiency.
My question to the developers is: when is this feature to be implemented
in Base?
I can't believe I am not the only user who has a need for this feature.
Any information on this will be appreciated.
BTW: Rekall does implement this feature, although it is not well
documented and Rekall does not seem to allow adjusting the column
widths. However, the data is visible to aid selection from the list.
Girvin Herr
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
