A datafile converted to 4Dv16 will have it's indexes rebuilt due to an update of the Unicode library. Also because a 4Dv16 datafile can be reopened with earlier versions of 4D, doing so will trigger the system to rebuild the indexes for the older Unicode library.

There may be a notice that the building of the global indexes may differ in speeds between 4Dv16 and earlier versions. This is because the global reindexing algorithm has been optimized even further which will provide faster speeds when the global indexes are rebuilt, this is also the case when the indexes are rebuild after a repair or if the .4dindx file has been deleted.

Related TechTip:
Data files opened in 4D v16 can still be opened in 4D v15