On Wed, 2024-10-30 at 17:43 +0100, Robert Großkopf wrote:
> Hi Harvey,
> >
> > Interestingly, exporting the 'virgin' report file as pdf retains
> > the
> > 'tick'/blank/minus symbols.
>
> You could also add UTF-8-Symbols. I do this in forms for Buttons.
> Something like ✅ (U+2705)🛑 (U+1F6D1) …
>
You will need to research documentation for mariadb syntax / functions,
I'm not familiar with it.
Base query editor will complain on SQL that is non-compliant to hsqldb,
but there is a "Passthrough" (or maybe "Native SQL") option on the query
editor that you can use to silence the Base parser and
Hi Harvey,
Interestingly, exporting the 'virgin' report file as pdf retains the
'tick'/blank/minus symbols.
You could also add UTF-8-Symbols. I do this in forms for Buttons.
Something like ✅ (U+2705)🛑 (U+1F6D1) …
Regards
Robert
--
Homepage: http://www.familiegrosskopf.de/robert
--
To unsub
Per my experience the - signs are likely null value. A boolean control
cycles through True / False / Null unless you specifically disable null.
On 10/30/24 11:25, Harvey Nimmo wrote:
Interestingly, exporting the 'virgin' report file as pdf retains the
'tick'/blank/minus symbols.
--
To unsubsc
On Wed, 2024-10-30 at 15:08 +0100, Robert Großkopf wrote:
> Hi Harvey,
>
> do ist this way:
>
> IF([myBitField];"yes";"no")
>
> OR
>
> IF([myBitField];"☒";IF(ISBLANK([myBitField]);"-";"□"))
>
> Add this code in Data → Datafield. Write the name of the field inside
> the brackets []
>
> Regards
On Wed, 2024-10-30 at 15:13 +0100, Robert Großkopf wrote:
> Hi Harvey,
>
> for using AutoGrow:
>
> 1. All fields in one row should have the same height and the same
> y-start. So it will become a row in the table, which will be created
> by
> ReportBuilder in Writer. Default height for every fi
Hi Harvey,
for using AutoGrow:
1. All fields in one row should have the same height and the same
y-start. So it will become a row in the table, which will be created by
ReportBuilder in Writer. Default height for every field is 0.5 cm here.
2. Mark the first field in the row as AutoGrow → Ye
Hi Harvey,
do ist this way:
IF([myBitField];"yes";"no")
OR
IF([myBitField];"☒";IF(ISBLANK([myBitField]);"-";"□"))
Add this code in Data → Datafield. Write the name of the field inside
the brackets []
Regards
Robert
--
Homepage: http://www.familiegrosskopf.de/robert
--
To unsubscribe e-m
Thanks! I suspected it might be be something like that.
I am using LOBase with a mariadb backend, so I an not sure how that
should be handled. In any case, the Query GUI does not like my formula
as is.
Cheers
Harvey
On Wed, 2024-10-30 at 08:13 -0400, Java Joe wrote:
> I have not tested, but wou
I have a report field that contains the following data Value
=[Ort1]&IF(NOT(ISBLANK([Ort2]));UNICHAR(13)&UNICHAR(10)&[Ort2];"")&IF(N
OT(ISBLANK([Ort3]));UNICHAR(13)&UNICHAR(10)&[Ort3];"")&IF(NOT(ISBLANK([
Staat]));UNICHAR(13)&UNICHAR(10)&[Staat];"")
As the field from the attached database query m
I have not tested, but would suspect it is evaluating the length of the
formula rather then the length of the content the formula produces.
If your data source is a query it should be possible to produce the
string you want in the query, then just reference the field instead of
using a formula.
I have a table in LO Base containing a number of fields of type
Yes/No[BIT]. A value entered in such a field appears as a 'tick',
(toggling between blank and 'tick') (By the way, 'minus' sign seems
also to be alternatively equivalent to a blank)
A report containing these tick values appears, as wa
12 matches
Mail list logo
