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.0430.641
The following release notes apply to Toolbox build 24.1.0430.641. G-Code Path Fix An issue was discovered wherein G-code would sometimes not generate along the correct path, with files never being created in secondary folders, even in circumstances ...
Microvellum Foundation Library Release Notes | Build 24.0419
Additions Added the new Blum SPACE STEP system. This can be activated within the “Toe Kick Assembly” construction option prompt in certain base & tall cabinet products. Added a new drawer system, the Harn Alunan T. Added 9 new Lamello Cabineo X ...
Toolbox Release Notes | Build 24.1.0416.641
The following release notes apply to Toolbox build 24.1.0416.641. Maestro Toolfile Fix There was an issue with Maestro SCM Toolfiles reportedly experienced by some users, wherein the labels output by autolabeling would be in incorrect positions, an ...
Toolbox Release Notes | Build 24.1.0409.641
The following release notes apply to Toolbox build 24.1.0409.641 Saw Delimited Processing Station Figure 1: The Saw Delimited option in a custom processing station. New options have been added to saw processing stations to allow for control over data ...
Toolbox Release Notes | Build 24.1.0328.641
The following release notes apply to Toolbox Build 24.1.0328.641 Fillet Token Fixes Issues were discovered in the use of fillet tokens on products that also had the IRIB setting enabled: Some users processed work orders with rounded parts, which ...