Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hello,

As already stated, I don't see a problem with what you have presented. I am basing this on you using MySQL as your database. Here is what you have show in the question so far (obviously this data is different than yours):

Report Query:

image description

Report Layout:

image description

and finally the running of the report:

image description

This was run on Linux Mint 18.3 using LO v5.4.3.2 and MySQL Server 5.7

There must be something else to your problem as I so far cannot duplicate.

Hello,

As already stated, I don't see a problem with what you have presented. I am basing this on you using MySQL as your database. Here is what you have show in the question so far (obviously this data is different than yours):

Report Query:

image description

Report Layout:

image description

and finally the running of the report:

image description

This was run on Linux Mint 18.3 using LO v5.4.3.2 and MySQL Server 5.7

There must be something else to your problem as I so far cannot duplicate.

Edit:

I have now been able to generate errors upon report execution:

image description

I was able to do this by simply switching to a different connection type. I typically use MySQL (Native) and simply changer to JDBC. This in turn then produced the error. The problem is in the connector.

If this answers your question please tick the ✔ (upper left area of answer). It helps others to know there was an accepted answer.

Hello,

As already stated, I don't see a problem with what you have presented. I am basing this on you using MySQL as your database. Here is what you have show in the question so far (obviously this data is different than yours):

Report Query:

image description

Report Layout:

image description

and finally the running of the report:

image description

This was run on Linux Mint 18.3 using LO v5.4.3.2 and MySQL Server 5.7

There must be something else to your problem as I so far cannot duplicate.

Edit:

I have now been able to generate errors upon report execution:

image description

I was able to do this by simply switching to a different connection type. I typically use MySQL (Native) and simply changer changed to JDBC. This in turn then produced the error. The problem is in the connector.

If this answers your question please tick the ✔ (upper left area of answer). It helps others to know there was an accepted answer.