Subject: | |
From: | |
Reply To: | |
Date: | Wed, 13 Oct 2010 09:42:15 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Andre
Create a new table with a single record and put your timestamp in that table. Then use a cartesian join to that table (a pipeline type join 1 = 1 sort of thing) and all users will get to see the same timestamp. You'll need to ensure users can't enter the field as they'll lock the record and cause grief to your script that sets the timestamp.
Stephen
----------
"I want WYSIWYG... I want it to support major browsers... I want it to reflect the spirit of the company ... I want a pony!" --- Michael Lopp
On Oct 13, 2010, at 9:22 AM, André wrote:
> I have a table of several thousand records and a global timestamp field. A user-activated script sets the timestamp field when it runs. However, other users can't see the value in the timestamp field, because globals are user specific, and thus can't tell when the script was last run. I'm stuck in a rut. Is there a way around this or another approach altogether? Can I have a timestamp field that applies to all records in a table and displays the same value to all users when set by any one user?
>
> The file is hosted on FMS 10 and clients are FMP 10, all on Macs, OS X 10.4-10.6.
>
> Thanks for any suggestions.
>
> Andre
|
|
|