Globals not as global as I thought

[Søren Dyhr]

I had set my hopes too high, when I had some autoenter fields containing:

Evaluate(Case(0;0);g_Something)

...note that I out of pure sloppyness/lazyness, use Case(0;0) instead of "" because I then can duplicate the fields and change type afterwards ...even into time or date.

But here comes the question, is there a way to prevent the autoenter to execute when creating a new record or duplicating?? In my ignorance did I believe that since we were talking about a global would it be like the same field every record, with no need to refreshing at all since it was global.

--sd

[Brian C]

I will give this my best guess;

Even though the content of the global field does not change, autoenter is always triggered by the act of commiting the field content to the record. I think the only way around it is to use the SetField script step to circumvent it.