It sounds like a screen refresh issue if the data viewer shows that it has the correct value, but you don't see it on the screen. An extra script step with refresh window might fix this.
Exactly how did you set up the "normal field's" calculation to get its value from the global field?
Why not just use the global field in place of this "normal" field?
Thanks for your reply. I tried refreshing the window but it didn't work. The normal field's calculation is just a reference to the global field.
I'm trying to view products per bill. It's a customers record with to portal's. One portal shows the different bills if i click a portal row a second portal will show the products that are on that bill. Beneath the second portal is that field that shows the Bill ID. The problem is if i use a global field and go to a new customers record who hasn't got any bills there's a value in the field below the empty portal. That value belong's to another customer and things could get confusing. The normal field prevents this problem, but another problem occurs. If i have 2 or more bills for one customer and click the portal row with the Bill ID, the products in the portal do change but the field beneath it shows the Bill ID from the previous bill. If you could help me solve this problem, i would be really appreciate it.
In what table is the global field defined and in what table is the calculation field defined?
Is it a calculation field or is it a data field with an auto-entered calculation?
There Both in the same table "Bills" and it is a data field with an auto-entered calculation namely the global field.
Because you asked if it was a data field or a calculation field i switched it to a calculation field and now my problem is solved!!!!
You've been great!!! Thanks a Million!!!!
For future reference, data fields with auto-entered calculations will not update automatically when a referenced field in a related table is modified--which appears to be the case here.
Great! Thanks for your advice