See Advanced Topics.
Database dates and times are stored with unspecified time zone information. This date and time model works perfectly for nearly all of our customers because computer networks are typically contained within a single time zone, so no time zone information is necessary. If all of the computers on your network (including your server) are within a single time zone, the information on this page doesn't apply to you unless you plan to expand your network to multiple time zones in the future.
In general, if you run into issues with timezones, first update Open Dental to the latest stable version, then contact Open Dental Support for input.
Middle Tier is not typically an issue with timezones. The MySQL server time may be used when logging some date or time stamps (e.g., Audit Trail); this may differ from the middle tier server.
If using Replication in different time zones, data will be synced but may not show at all locations.
If you are using a Remote Access app to access an Open Dental database, you may notice that your workstation is using the time zone of the database you are remotely accessing, rather than your local time. This will affect features in Open Dental such as the horizontal time line in the Appointments Module.
If this happens, the solution is to create a group policy to direct the remote server to use the local time zone on the user's workstation for software applications like Open Dental. Note that most times recorded in Open Dental are not affected by group policy, because they use the time zone of your MySQL server and not the workstation time.