Greetings,
I think I have a solution. I did some research on the Pentaho report
generator that is used in the LO Base Report Generator with emphasis on
their formula syntax. The following formula placed in the report field's
properties "Data" tab in "Data field..." seems to do what I need:
Hello Robert
See below.
Hello Robert
See below.
On 5/16/2019 2:53 PM, Robert Großkopf wrote:
Hi Paul,
When I want to append a Table from database one to database two, I get
the message "No corresponding column type could be found for column
'ID'."
The field "ID" from the Firebird-table
On 5/16/19 11:12 AM, Johnny Rosenberg wrote:
Den tors 16 maj 2019 kl 00:22 skrev Girvin Herr :
Greetings,
I am using LibreOffice 5.3.4.2 on Slackware Linux 14.2 (K4.4.75).
I have a database with a text field which may or may not be null. What I
want to do is to prefix a dash "-" before the
Hi Paul,
>
> When I want to append a Table from database one to database two, I get
> the message "No corresponding column type could be found for column
> 'ID'."
The field "ID" from the Firebird-table must be autovalue.
I you will import the table, which all contains text-fields, the wizard
Hi Girvin,
the Report-Builder should better get this information from the view,
which is datasource of the report. All what could be done through SQL
before submitting the data to the report will work faster (and mostly
better).
You have to write in SQL
SELECT '-'||"text" FROM "table"
This will
Windows 7 64 bit, Version: 6.2.3.2 (x64)
I have two databases.
Both have "ID" defined as the first field in the databases.
The first database is an import of text files that is unregistered. I
believe it is Firebird, but do not know how to confirm this. The header
to the text file has "ID"
Den tors 16 maj 2019 kl 00:22 skrev Girvin Herr :
> Greetings,
>
> I am using LibreOffice 5.3.4.2 on Slackware Linux 14.2 (K4.4.75).
>
> I have a database with a text field which may or may not be null. What I
> want to do is to prefix a dash "-" before the text if the text field is
> not null.
Remy,
Greetings.
I tried your suggestion, but it didn't work as expected. LO Report
Builder did replace "[<>""]-@" with
"[<>0]-@;General", similar to what you experienced. However, the result
is strange and almost indeterminate. Sometimes if the text field is
alpha-numeric, the result is "-"
Hi Girvin,
>
> However, when I try these parameters in the new report, when I select
> "Accumulation" in the Function field, it changes "Data Field" to
> "[AccumulationCostReport]" and the Function and Scope fields go blank.
Seems to be the right function. You could see the content of the
