Globals and Autoenter Modification

[Drew Sanderson]

If I enter a new value into a global field does the autoenter modification information change for all the records in a table when the global changes?

Thanks,

Drew

[BobWeaver]

No. Changing a global won't trigger any autoenter updates.

[LaRetta]

a global won't trigger any autoenter updates

... except on the record currently being modified.

Edited October 10, 2006 by Guest
Changed 'field' to 'record'

[comment]

I don't think so.

[LaRetta]

I misread the post, thanks for the correction.

I was thinking the global was within ANY field with Auto Enter. It doesn't matter whether the field is indexed and will even work if 'Do not Replace Existing Value' is CHECKED. Using trigger would look like:

Let ( trigger = globalField ; thisField )

Because as trigger, a change to the global will change the field it is referenced in. And ANY field change will trigger modification. But of course it can't see other records and I was running on an incorrect assumption (global was in auto-enter) anyway. :

[Søren Dyhr]

A fair share of these global questions (FAQ's) fall into tagging records for being over due, well searches can establish such facts ...but a reporting shy would like to eyeball every one and each. But wouldn't it be easier to establish a non equi selfjoin portal showing records falling in between upper and lower dates in a range controled by current date - such as:

Get ( CurrentDate ) - 60 ...as one threshold,and:

Get ( CurrentDate ) - 90 ...as the other one.

The poral will work pretty globalistic in behaviour during the day!

--sd

[BobWeaver]

Good point LaRetta. I was only thinking of autoenter times, dates, timestamps, etc., but Drew may have intended calculations like your example.

[Drew Sanderson]

That is all helpful. Thanks for the replys and conversation. I definiely learned something. In the mean time I implemented a different solution to my problem. I was going to have FM insert a calulated value from a record to a record after searching based on the modifcation timestamp. I instead just had the id of the current record inserted via calculation into the global field. Then from the other table the script calls for inserting the calcualted value which is the value in the global field. Not sure if that made sense but regardless it works well.

Thanks All.