Use Server time for Now()

[Guest]

Hello,
I'm using Access 2002, FE and BE. I use the simple statement of Now() to
populate a modified time. Unfortunately, some of my users are in different
time zones.

Is it possible to reference the BE server time instead of the user's
computer's time?

example returns user's computer time
me.modify_time = now()

 

[Stefan Hoffmann]

hi David,

I'm using Access 2002, FE and BE. I use the simple statement of Now() to
populate a modified time. Unfortunately, some of my users are in different
time zones.

http://www.cpearson.com/excel/timezone.htm

Just save the time zone in an extra field.

Is it possible to reference the BE server time instead of the user's
computer's time?

Afaik no, you have to implement NTP.

mfG
--> stefan <--

 

[Rick Brandt]

Hello,
I'm using Access 2002, FE and BE. I use the simple statement of
Now() to populate a modified time. Unfortunately, some of my users
are in different time zones.

Is it possible to reference the BE server time instead of the user's
computer's time?

example returns user's computer time
me.modify_time = now()

A split Access app works horribly over a WAN and is almost certain to become
corrupted so I fail to see how you can have users in different time zones and be
using a standard split app.

If you were using a server back end like SQL Server then this problem is easily
solved or if you were using terminal services to have everyone run their FE
remotely on the server then that would also solve the problem.

Believe me, different time zones will be the least of your troubles if you try
to run Access over a WAN connection.

 

[Guest]

Thank you Stefan, looks like it will work well.

hi David,

http://www.cpearson.com/excel/timezone.htm

Just save the time zone in an extra field.

Afaik no, you have to implement NTP.

mfG
--> stefan <--

 

[Guest]

Rick I must be living on borrowed time. Not sure if it is the company
network or my design. Perhaps a combo of both. But it has been rock solid
for 2 years now, with about 10 users thousands of miles from the server, and
30 users within the same building as the server. Unfortunately, the remote
users are at about 1/2 speed from local users, but no corruption. For me,
1/2 speed worked better than trying to create a program to synch up data.

Initially the database corrupted frequently, however thru the help of this
newsgroup and Access Developers Handbook, it works.
I have F/E and B/E with the users opening mde from their local drive.
Using Tony Toews Front End Updater and launching the MDE as Runtime.
Normalized and indexed well.
Strictly followed the good development practices of Allen Browne.
Tried to lock down the short cut keys and user's access to objects. Just
about everything short of User Level Security. Data security is not a
concern.

 

[Rick Brandt]

Rick I must be living on borrowed time. Not sure if it is the company
network or my design. Perhaps a combo of both. But it has been rock
solid for 2 years now, with about 10 users thousands of miles from
the server, and 30 users within the same building as the server.
Unfortunately, the remote users are at about 1/2 speed from local
users, but no corruption. For me, 1/2 speed worked better than
trying to create a program to synch up data.

Initially the database corrupted frequently, however thru the help of
this newsgroup and Access Developers Handbook, it works.
I have F/E and B/E with the users opening mde from their local drive.
Using Tony Toews Front End Updater and launching the MDE as Runtime.
Normalized and indexed well.
Strictly followed the good development practices of Allen Browne.
Tried to lock down the short cut keys and user's access to objects.
Just about everything short of User Level Security. Data security is
not a concern.

With more than one free SQL Server option that would handle that number of users
I just can't see any reason to keep your fingers crossed and use a Jet back end
in that scenario.

(Murphy might be sleeping, but he ain't dead)