Hard to say from here without more detail.
But lookups physically copy data from the related lookup table into the table doing the lookup. Updating data in the look up table will not automatically modify data already copied into the other table. Only a record that is created after the change would automatically show the new value.This is generally why you would use a look up or auto-enter calculation to copy over data from such a table in the first place. Other methods would be used if you want this data to automatically update each time a corresponding change is made in the look up table.
Lookups triggered by setting the key(s), also called match field(s), in relationship on which the lookup is based.
In your scenario, it's not clear if you have something like a TRIPS table that has start and end miles that does a lookup from the RATES table (or something similar).
If you can, just put one of the fields from the primary table that's in the relationship to the lookup table on the layout, then select that field and go to Records menu and select "Relookup Field Contents." Then look for "Relookup Field Contents" in the Script Workspace.
Let us know if this works.
What about using a caluclated field instead of a lookup. If you make the calculation unstored it will do this 'lookup' for you when the record is opened.
Since my reading indicates that is what you want to do, use the calculation.
1 of 1 people found this helpful
You have to select the match field and then select relookup from the records menu to get it lookup new values. or change data in the match field. otherwise the data not changed even though the data in the lookup table is changed.
i.e. you sale tax rate changes part way through the year the new rate on applies only to new sales, not old ones. and lookups are the way to go for this. but, if the data need to change in old record as the table is updated then lookups are not the best way. and what &gofmp15 said is better.
You could also make as simple script to do the relookup.
goto layout (that needs the new info)
show all records
goto match field
and use on layout exit script trigger to update your records.
There are several problems with using lookup fields for more than a one time lookup.
Should existing data be changed, a particularly sensitive question with invoices when prices or taxes change.
What happens when the lookup file is changed but the fields in your parent file haven't been relooked up? If the data is supposed to be real time, this can be a problem. If so, then an unstored calculated field might be a better idea.
Then of course is the question of whether or not you need to lookup the data in the other file. If you have a relationship then any changes would be shown 'instantly' if you drag a related field onto your layout.
Thanks for all the help here, let me explain the issue I'm encountering.
This is the table I have. I updated the "RatePeMile" column and everything still calculates according to the the Start and End miles. When I update the Start and End miles, only the first two rows calculate according to the rate of $12.34. Any rows after the 2nd row will continue to calculate at $12.34, For example: 301 miles will calculate at $12.34 rather than $9.51.
You'll need to show us those calculations and tell us whether they are in calculation fields or number fields with an auto-enter calculation.
The "cost" calculation field is (miles * milesamount)
The "miles" is a number field
The "milesamount" is a lookup field which looks up from the table mentioned.
I see no "miles amount" value to look up from the table in your earlier reply.
It looks up the "RatePerMile" from the table.
If I was to change all the Start and End values and leave the RatePerMile cost the same. They calculate, but immediately when I change the RatePerMile cost, it would only calculate the first two rows correctly.
I have a few other tables in our database and noticed the same thing occurring.
What I am looking for is the precise values and calculations used. The calculation you describe in reply #9 does not refer to the rate you say that it looks up. So what is the actual calculation that uses this looked up rate?
I prefer not to guess.
Hi philmodjunk, I apologize, I'm jumping in to this database trying to figure out how to update the table and calculate based on the miles.
I'm not quite sure what the precise values and calculations are being used. It's a big mind boggling to not understand why it would only grab the correct ratepermile for the first two rows based on the start and end miles.
I did find a script that updates the tables, but running the script did not update the rates either.