The problem here is that the views are connected directly to the models.

Although this sounds horrible to achieve in delphi, the first step is to enforce a separation of concerns.

You could use a MVVM approach and have intermediary view-models that perform localised transformation of database values for display. These same view-models can transform localised input into the timezone the database expects when storing data.

The upside of all this work is that future localised changes will be much, much easier to accomplish.

The problem here is that the views are connected directly to the models.

Although this sounds horrible to achieve in delphi, the first step is to enforce a separation of concerns.

You could use a MVVM approach and have intermediary view-models that perform localised transformation of database values for display. These same view-models can transform localised input into the timezone the database expects when storing data.

MVP or some other MV* variant might be better suited depending on how you're currently set up and your exact requirements, but you get the picture. The upside of all this work is that future localised changes will be much, much easier to accomplish.