I stumbled into this today and I never realized or noticed it before, so I just wanted to know if this is the normal behavior.
When defining a property the that has a dynamic reference, does the location of the define_com (in the source) for the component matter?
For example:
When the component is defined before the property
but when the component is defined after the property
I get an error.
Is this normal? Like I said I've never seen it before.
Component and Property Source Order
- Stewart Marshall
- Posts: 417
- Joined: Thu Nov 05, 2015 5:25 pm
Re: Component and Property Source Order
Hi Joe
The Get portion of the Property definition seems to be OK, but as soon as the Set is added the sequence of the declarations becomes important.
This is perfectly normal, albeit a little strange.
LANSA is quite flexible in where it lets you define certain things, but best practice is always to put declarations above the place where the variable is used.
Regards
The Get portion of the Property definition seems to be OK, but as soon as the Set is added the sequence of the declarations becomes important.
This is perfectly normal, albeit a little strange.
LANSA is quite flexible in where it lets you define certain things, but best practice is always to put declarations above the place where the variable is used.
Regards