It's just plain old VFP updating tables. The problem is that a user from

EST zone stamps a record at say 11:00 AM local time. A user from PST

stamps a record at 10:00 AM local time (1:00 PM EST). The 10:00 AM time is

in the change queue as before the 11 AM entry, even though it occurred

later. This code wasn't written to handle updating from different

timezones, the old system ran on a terminal server that everyone logged

into that was EST, so all times were EST.

Now, everything is on the cloud, and the times are local to where the user

is at, hence the problem.

Fred

On Tue, Feb 7, 2012 at 9:49 AM, Tracy Pearson <tracy@powerchurch.com> wrote:

> Fred Taylor wrote on 2012-02-07:

> > Thanks Paul. That may be the route that has to be taken. I'm just not

> > that comfortable with that massive a change.

> >

> > Fred

> >

> >> We've moved a bunch of applications to the cloud and now have users

> >> accessing from multiple timezones, but the application wasn't built to

> >> handle that.

>

> Fred,

>

> Are they writing to the data in the cloud directly, or is there a middle

> point that can be changed to handle the incoming request and adjust the

> date/time stamps?

>

> Tracy Pearson

> PowerChurch Software

>

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/CAJCBksrx7=m4g=8UapHvXUa9BnGxc8DEOHsoHmrrdj3fEcJ3EQ@mail.gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.