Issue loading pages when text stretches over a page
Hi,
I've encountered an issue in RB Pro 15.04 (+ Delphi XE5 + NXDB V4.0005).
When we generate a report containing a DBMemo, and the text extends by
up to 6 lines (may be different for others) over to the next page, the
report remains in a busy state and locks out all controls except the
'last page' button.
The only way out is to try and display the last page, after which it
responds normally again.
If the text goes beyond that 6 line extension, the report loads fine. It
is only when it stretches that 1-6 lines over a page do you see this issue.
The DBMemo field properties has Stretch enabled. All other Layout
properties are either unticked or 0. It also does not shift relative to
any other components on the report.
Has anyone encountered this?
--
Regards,
Will Owyong
(GMT+10, Australia)
I've encountered an issue in RB Pro 15.04 (+ Delphi XE5 + NXDB V4.0005).
When we generate a report containing a DBMemo, and the text extends by
up to 6 lines (may be different for others) over to the next page, the
report remains in a busy state and locks out all controls except the
'last page' button.
The only way out is to try and display the last page, after which it
responds normally again.
If the text goes beyond that 6 line extension, the report loads fine. It
is only when it stretches that 1-6 lines over a page do you see this issue.
The DBMemo field properties has Stretch enabled. All other Layout
properties are either unticked or 0. It also does not shift relative to
any other components on the report.
Has anyone encountered this?
--
Regards,
Will Owyong
(GMT+10, Australia)
This discussion has been closed.
Comments
We have not seen this behavior before with RB 15.04. If possible,
please create a simple example (using only RB and Delphi components and
an in-memory dataset if necessary) that recreates this behavior and send
it to support@digital-metaphors.com in .zip format so we can take a look.
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Hi Nico,
I have worked out what the issue is but will send you an example
regardless as I'm not sure how to implement a workaround to it.
--
Regards,
Will Owyong
(GMT+10, Australia)