Mike Matthews omnis at lineal.co.uk
Wed Apr 1 11:23:54 EDT 2009

Thanks Kelly,

Can't quite find that info, but your other email did lead me to look  
at the session properties.  This is new stuff for me as no reason to  
venture there before.  If I turn off $usetimezonename and add a  
£timezoneoffsett, then all my old records are fine.  I guess this  
would be ok if all my data came from the same timezone for ever and  

Odd however that DateTime fields are all ok, it is just Time fields.

As this is a diary table, I could store the date and time in a  
DateTime field and split them on viewing.



On 1 Apr 2009, at 15:46, Kelly Burgess wrote:

> Hi Mike,
>> I have a few Time fields that will change the value from Frontbase  
>> when the clocks change, ie, they have gone forward 1 hour, so we  
>> are all late.'
> Per the "FrontBase V3 DAM.htm" docs:
> "It is recommended that applications adopt the use of the symbolic  
> $timezonename and do not use $timezoneoffset. Use of an absolute  
> offset can cause values returned from TIMESTAMP columns to be out by  
> one hour due to a change in daylight savings time."
> Kelly
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com

More information about the omnisdev-en mailing list