I have a Count field, a CountDate field, and a global CountDate field. When Count is changed, I want to enter the global CountDate into the standard CountDate field.

I was using CountDate auto enter =

Evaluate("gCountDate"; Count)

but then I changed the global field name and things went haywire, until I hunted the issue down. I'd like to have the option of changing field names.

So I tried =

Let([

C = Count

];

gCountDate)

but that triggered whenver gCountDate changed too.

Ideas?

More info is required, why is globals chosen over a relational say aggregate function?

--sd

Put the global date in another table.

comment,

Good idea, but the field is doing double duty, both an an auto enter and as the basis for a relationship. I'd like to keep it that way if possible.

I believe you could use an unstored calc = gField for the relationship, but I am not sure I fully understand the problem.

I'm looking for a calculation that will update a an auto enter field with the contents of a global when a third field changes with the following conditions: All fields are in the same table and I can change the name of the global field without having to change the calculation.

Sorry, but what you describe is an abstract riddle, not a real problem. Why do all the fields have to be in the same table? If we knew the real problem behind this, perhaps the solution would NOT have all the fields in the same table - but it would solve the problem at hand nevertheless.

P.S. I am only guessing now, but it seems to me your auto-enter should NOT have 'replace existing value' enabled.