I understand that in FB2 fields in triggers have been made read-only
where field modifications in triggers will not save. This includes all
OLD. fields, and all NEW. fields in after-update and after-insert
triggers.

We have used these fields as local variables in a lot of places, so a
lot of apps will fail to work in FB2. We will have to trawl throuh all
the metadata looking for instances, declare local variables, and copy
these fields into them. There is no simple way of finding them, and FB2
seems happy to accept scripts which include the error..

Is there a good reason for the change? As far as I can see it just
reduces flexibility and makes code more verbose.

Roger Vellacott
Passfield Data Systems Ltd