My Enterprise Server is sitting in Florida (Eastern Standard Time) and my QA team is in California (Pacific Time). They found if they make an appointment at noon, reload, it shows up at 9am. I checked the database in Florida and it believes the appointment as saved at noon Eastern Standard Time. Somehow, the point of saving and the point of loading the data is missing the time zones.

I’m very surprised no one else has had this problem or anything about it being mentioned in the manual. That usually makes me think I’ve missed something incredibly obvious. My fields are just standard SQL Server date/time fields. I think my issue comes from the fact that I use Stored Procedures to insert/update/delete rows. I suspect the values are beings set in California, shipped to Florida across the time zones and then saved there as if it happened in Florida. When it loads them back up, seems aware that it loaded them in Florida so it should change the values to Califorina time.

I could create some sort of off-set, time zone difference function for date fields way down in the guts of my app before it saves but there must be an easier way. Shouldn’t ES know that the client is in a different time zone and handle this in both directions? I would think the enterprise client would be able to help out too. Any ideas?