@record , {dict field name} and defprop/invalue (OpenInsight 32-Bit)
At 29 JUN 2004 04:44:45AM William Ng wrote:
I have read the "Converting Advance Revelation applications to Openinsight:Perspective from Developers".For symbolic fields it recommend one workaround of using {} operator instead of @record on page 9.The question i have is, if i use defprop instead of text, then my @record will be uptodate, right? If so, do i still have to change to use {} operator instead of @record?
At 29 JUN 2004 07:53AM Aaron Kaplan wrote:
It should be.
The Sprezzatura Group
World Leaders in all things RevSoft
At 29 JUN 2004 07:53AM Bob Orsini wrote:
It is recommended that you use {} when using fields on screens. The @record record does not allways update in windows.
At 29 JUN 2004 09:33PM William Ng wrote:
If i need to access data/field from the same table but not displayed on the screen for eg. the last year sales field(not in the screen) and a customer type field( in the screen) to decide what discount structure to give, do i use {} for the customer type field and @record for the last year sales figure?
At 29 JUN 2004 09:38PM William Ng wrote:
Sorry, i dont understand.
It should be that the @record will be uptodate if i use defprop and i dont have to change to {} or it should be what bob said that i should use {} for fields displayed on the screen?What about fields that are not displayed on the screen?
At 30 JUN 2004 07:56AM The Sprezzatura Group wrote:
If you want to feel save, use the braces, but I've not had troubles with @RECORD since around 3.1 or so.
The Sprezzatura Group
World Leaders in all things RevSoft