RB17 TableGrid
Just installed RB17Ent in DXE8Pro. Decided to try using a TableGrid in a
current report. There seems to be little if any info available for the
component other than RB Help which doesn't say much about "how to" usage.
When I drop the control on the report in designer, it defaults to one
row and three columns. What is the proper procedure for adding columns
and/or rows to the grid? If I right-click on the object in the report
tree, then click Column/Add, I get an immediate "List index out of
bounds (3)" error. Same result if I modify the ColCount property
directly. It's interesting, however, that the report tree shows that a
new column has been created, but if I click on it (or any other column
object at that point) I get an Access Violation.
If I do nothing else, close the RB Designer, then try to close Delphi, I
get the same "List Index..." error several more times, before Delphi
actually closes with another AV (EInvalidPointer).
Any ideas what I might be doing wrong?
Thanks.
current report. There seems to be little if any info available for the
component other than RB Help which doesn't say much about "how to" usage.
When I drop the control on the report in designer, it defaults to one
row and three columns. What is the proper procedure for adding columns
and/or rows to the grid? If I right-click on the object in the report
tree, then click Column/Add, I get an immediate "List index out of
bounds (3)" error. Same result if I modify the ColCount property
directly. It's interesting, however, that the report tree shows that a
new column has been created, but if I click on it (or any other column
object at that point) I get an Access Violation.
If I do nothing else, close the RB Designer, then try to close Delphi, I
get the same "List Index..." error several more times, before Delphi
actually closes with another AV (EInvalidPointer).
Any ideas what I might be doing wrong?
Thanks.
This discussion has been closed.
Comments
I researched this and it’s a Delphi design-time bug - one that I thought I
had fixed in pre-release testing. We're working on a new RB 17 build to
resolve this issue and a few others.
The error does not occur in the run-time designer, in case you're interested
in a work around.
Best regards,
-
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com