Hi.

In my database I have a small script that acts as an activitiy log, whereby as each user moves to and from particular screens or specific record activity, a new record is written to one of the tables with the user's login name, time & date, etc. It works great... except... (theres always a but) - the time recorded in the table is that of the client's workstation - which is fine except for several clients are operating in different timezones so the order of the log gets out of whack.

I have considerded a few options to get around this, but none will work satisfactorily. They included having a table that contains the timezone of that user - but they may change offices.

The only credible one is to have the server itself have an open table with a field that is it's own time and pull the info from there, but that means have FM (not FMS) running on the server as well, and seems like a clumsy solution.

Any ideas please peoples?

Cheers,

Greg

Hi.

In my database I have a small script that acts as an activitiy log, whereby as each user moves to and from particular screens or specific record activity, a new record is written to one of the tables with the user's login name, time & date, etc. It works great... except... (theres always a but) - the time recorded in the table is that of the client's workstation - which is fine except for several clients are operating in different timezones so the order of the log gets out of whack.

I have considerded a few options to get around this, but none will work satisfactorily. They included having a table that contains the timezone of that user - but they may change offices.

The only credible one is to have the server itself have an open table with a field that is it's own time and pull the info from there, but that means have FM (not FMS) running on the server as well, and seems like a clumsy solution.

Any ideas please peoples?

Cheers,

Greg

Try:

Get ( CurrentHostTimeStamp )

Try:

Get ( CurrentHostTimeStamp )

Oh dear. How embarassing. How does one blush online?!

Thankyou. :)

You could also just use the Access.log that is generated by FMS itself. With a small OS level script you can move a copy of it to the FMS docs folder and have FMS import it into your desired table. Doesn't burden your solution and works across all your hosted files....

Hi Wim Decorte,

That sounds like a good solution too - straight from the core as it were. I will look at that.

Thank you.

Greg