UDT created then referenced in a DB, changed UDT, DB error?

Changing a UDT, when your program is in an advanced stage, is a sensitive matter because it changes the UDT objects size in memory and therefore a complete address change of variables which are defined through that UDT. It creates a complete memory address offset for all variables.

If program size is small then you can manage the DBs manually. Just open the DB in which that particular UDT is used. You will see the changed UDT objects in red color. Right click on the object and select ‘Update declaration’. But in large programs, it is difficult to manage this so define UDTs with complete planning (and before actual programming) to avoid future changes.

You can manage it easily by doing either check and update access in each individual block.
Or doing a complete check block consistency (Compile all).

Compile all will solve more than 50% or 60% or maybe more of time stamp conflicts.
I made a small test for modifying a UDT and performed a check block consistency (Compile all).
It solved data blocks declaration problem and updated data blockssuccessfully.
It just couldn't deal with UDTin functions (couldn'tupdate actual parameters).
By switching addressing type (From default to symbolic addressing has priority), modify UDT, compile all, everything works fine.
It looks easy but you must paya lot of attention when you modify variables'symbols and sizes.