Anna - When addressing date/time display issues, it is useful to know what time zone the date/time data was originally recorded in. The server machine that is capturing the data is set to a specific time zone, and all data reported worldwide that originated on that server is always in that time zone. For example, Microsoft Atlas data is always recorded in Eastern Standard Time.

Once you know the 'native' or 'original' time zone of the data, you can address the issue of what should be displayed when the file is opened in other time zones around the world. If you have appended date/time data from different sources into a single field/column, it is important that the data first be synchronised to the same time zone.

To check this, you must change the display format of the Date/Time field to display the time zone that the data was recorded in.

Anna, there is a known limitation with the "EEEE" format when used this way. If you remove the date+month+year fields, Omniscope can no longer model the field correctly as a Date data type.

This is a similar issue to: http://forums.visokio.com/discussion/comment/3448/#Comment_3448

If you want the field to be typed 'Date', you must include the full date/month/year aspects so Omniscope can determine which day name it is by the other aspects. For example, "yyyy-mm-dd, EEEE".

Or, instead of duplicating and changing field type, you should add a new field and set a formula DATETOTEXT([Date], "EEEE"). You will end up with a Text/Category (not Date) field containing just the correct day names.

Thanks Steve