Which triggers are you using ?
fieldsyntax is an occurrence level property.
Use Deserialize triggers to apply changes or secure dynamic changes done before in the Serialize triggers
I have this example:
In the preSerialize trigger (Pre Save Occurrence in Uniface 9.7)
if ($dbocc(EDATA) )
fieldsyntax FLD1.EDATA,"NED"
else
fieldsyntax FLD1.EDATA,"YED"
endif
and in the postDeserialize (Post Load Occurrence in Uniface 9.7)
if ($occcrc(EDATA) != "")
fieldsyntax FLD1.EDATA,"NED"
else
fieldsyntax FLD1.EDATA,"YED"
endif
Now existing occurrences can't be changed and new occurrences can be changed.
------------------------------
Peter Beugel
Rocket Internal - All Brands
Amsterdam NL
------------------------------
Original Message:
Sent: 02-18-2022 07:09
From: Iain Sharp
Subject: DSPs and dimming fields.
#uniface-10
I am trying to dim and resurrect a field in a DSP in response to user actions.
I was trying $fieldproperties(field)="html:disabled" (which I thought is what the help pointed to) without success.
I can dim the field with $fieldsyntax(field)="DIM" which successfully sets the disabled attribute.
However, neither $fieldsyntax(field)="" nor $fieldsyntaxt(field)="YED,YPR" nor $fieldproperties(field)="!html:disabled" seem to do the trick for allowing entry again.
What is the trick to remove the disabled attribute? (preferably from proc code but I suppose I can incorporate a weboperation if necessary.
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------