Can someone explain to me the limitations of Auto-Entering
calculations? I have an Orders table whose primary layout contains a
portal to a related database LineItems.

In Orders I have two fields, City and TaxRate. TaxRate is set to
AutoEnter a calculation based on a Case statement for City. I've set
the checkbox so that it will replace the field if the City is changed.
That works great. However, that effect doesn't work on another set of
fields.

Both Orders and LineItems have fields named DateOut and DateIn. I want
those two fields in LineItems to grab the same dates from their
respective fields in the Orders table and to update if those Order
fields should change. I also want the ability to change LineItem dates
individually (hence no calc field). What worked with City and TaxRate
in Orders is not working across tables between Orders and LineItems.
Nor does it work off a calculation within LineItems (I set up a calc
field to pull the Orders date, then tried the Auto Enter off that
field).

All calcs are set to dates, all fields involved are date fields.

Any ideas of how to make this work? Are this limitations (unable to
AutoEnter a calc across tables or off a calculation) normal?


Thanks,
-G

What your looking for is a calculation that will update whenever a
field in another table is changed. This exists, unfortunately it's an
unstored calc.

The auto-enter allows you to get data from a different table and store
the value BUT only on record creation.

Unchecking the checkbox "Do not replace existing value" will
recalculate the value, including data from other tables, if at least 1
of the fields referenced in the calc is a stored field in this table
eg. modification time-stamp.

So to answer your question; can you store a value in a record in table
B that updates automatically when a record in table A is changed
without touching record B? - NO
But if you can trigger any change in record B, then it can be done.