Using Component Properties
The properties of any component within a report can be used
when creating expressions.
Syntax
Whether the report language is VB.NET or C#, the syntax
is the same: The name of the component and the property name separated by a
full-stop character or a decimal point, within curly braces.
{Component.Property}
VB.NET is not
case sensitive, while C# is case
sensitive. To access a calculated value from a component, use the property that contains the result you need. For instance, if the component has
a hyperlink value which calculates a hyperlink from the other component
properties, you would enter the expression:
{MyComponent.HyperlinkValue}
When necessary, you can use the component properties in calculations. The following example would show the area taken up by the
component:
{MyComponent.Width*MyComponent.Height}
Related Articles
Auto-Sizing Text Components in Report Designer
The articles in this section of the Knowledge Base involve working with Auto-Size properties in Report Designer. To learn additional information regarding Auto-Sizing properties, see Understanding Auto-Sizing Properties in Report Designer. This ...
Report Band Properties in Report Designer
The articles in this section of the Knowledge Base involve working with Report Bands for display in your reports. To learn more about Report Bands, and how to access this section within the Report Designer, see Understanding Report Bands in Report ...
Understanding Pages in the Report Designer
The articles in this section of the Knowledge Base involve working with Pages in your reports. To access the Report Designer, select Toolbox Setup > Design Reports > Design (Report Type) Report. Select New Report to design a report from scratch or ...
Image Component Stretch Property in Report Designer
The articles in this section of the Knowledge Base involve working with Images for display in your reports. To learn more about Images, and how to access the Image component within the Report Designer, see Loading Images in Report Designer. This ...
Text Properties in Report Designer
Word Wrap Text that cannot fit on one line is trimmed by default. To avoid this, and allow text to fill multiple lines, set the TextOptions.WordWrap property to True. Horizontal and vertical alignments are used when the text is wrapped on a new line. ...
Recent Articles
Toolbox Release Notes | Build 24.1.1105.641
The following release notes apply to Toolbox build 24.1.1105.641 Nesting Fix Fig. 1: The fatal error that would occur during processing. There was reportedly an issue that occurred when clients attempted to process a work order using the nesting ...
Microvellum Foundation Library Release Notes | Build 24.1025
The following release notes apply to Microvellum Foundation Library build 24.1025. Additions Added new global variable “Remove Stop Dado On Bottom Edge” for wood drawer boxes. Check this option to run the dado through at the bottom of the sub front ...
Toolbox Release Notes | Build 24.1.1030.641
The following release notes apply to Toolbox build 24.1.1030.641 Routing and Profile Fixes Several issues were found with routing and polyline paths: Fig. 1: Horizontal routes off of a part disappearing (left) and appearing correctly (right). When ...
Toolbox Release Notes | Build 24.1.1010.641
The following release notes apply to Toolbox build 24.1.1010.641 Biesse Winstore Fix Several issues with the Biesse Winstore plugin have been resolved: There was an issue that would sometimes occur wherein materials that were intended to stack wound ...
Toolbox Release Notes | Build 24.1.1001.641
The following release notes apply to Toolbox build 24.1.1001.641 HBore Toolfile Fix Fig. 1: The location in the Toolfile UI where the error would occur. There was an issue reported with the functionality of the Horizontal Boring Machine setting in ...