Date issue for users in other country

[tet_hadavas]

Dear List,

All our servers are in the United States. Our users in Japan are going to go-live soon and they'll access OneWorld through the citrix server. Now they have our date and time stamp, how do I get their local date and time?

Thanks in advance for your help,
Tet Hadavas
OneWorld Xe, SP 17.1, Win 2000, SQL 7

 

[Tom_Davidson]

Tet,

This has been an issue for us since day 1. It is one of the changes we
have been asking JDE to implement in base software for 2+ years now. As
far as we know there is no way to do this and maintain the integrity of our
date/time stamps.

We found 2 possible solutions:

1) Use GMT as this is the only recognized international standard. This is
the one we chose.

2) Use dateline time. This has the 'advantage' that a day is a day. The
down side is you still have to code display dates, but it makes writing
reports based on date easy.

HTH,

Tom Davidson
Xe U1 SP 17.1D; AS/400 V4R5; CO on SQL 7; TSE Metaframe 1.8a




All our servers are in the United States. Our users in Japan are going to
go-live soon and they'll access OneWorld through the citrix server. Now
they have our date and time stamp, how do I get their local date and time?






OW 7332 SP 11.3VER, NT 4.0 SP 5, TSE 4.0 SP 4, Metrframe 1.8, CO SQL 7.0

 

[mjf]

Tet

Like Tom we have the same issue with our offices in Europe, USA and
Singapore. We tried using the "Client Time Zone" features of Citrix but
abandoned it very quickly. The reason being that we got licensing errors at
sign on when the Citrix server was in one time zone and the clients were in
another. As soon as the date changed in NZ (we are 12hrs ahead of Europe),
the European users could not log on.

In the end we maintain transaction integrity only by the user actually
entering the dates they want on transactions rather than letting them
default to the system date. Our overseas users are very aware of it and are
pretty good at getting it correct. We haven't come across any issues with
the date time stamp on transactions or the date on reports.

We decided not to go to GMT because by far the largest number of users are
in NZ. Basically the power of numbers rules.

Regards

Marty Fleming
Business Analyst
Richmond Limited

Phone: +64 +6 8786464 Ext 8168
Fax : +64 +6 8780959
Email: mailto:[email protected]

OneWorld: Xe SP16.1
Database: Oracle 8i
Enterprise Server: Compaq Proliant 8500R W2K

 

[mark_hindle]

Tet
What we also are NZ based and have offices in the US and the UK.
What we have done is dedicate a terminal server in the New York time zone for these users, then at least their clients have the correct date. For any UBEs that the run that rely on the date we have an NT logic server also in the NY time zone for those users. This is mostly an issue for Invoice print.
Everything else is done in the New Zealand time zone, which covers our offices in NZ, Australia, and Singapore.

Mark

Xe-AS/400 es
NT4 Logic and CO
W2K TS