Lookups

[Carri]

Please can someone clarify this for me:

What's the difference between setting a field as a lookup to a field in another table

AND

Making that field a calculation (in a text type) to be = to that other field?

Here's my problem.

Initially I need the field to lookup the values from the other table, but I only want that to happen once, once those values are in the new table I want users to be able to change them without risking loosing the changes when the original field is reselected.

e.g. When an activity is selected from a list (TABLE:Program), the activities default resources are stored in TABLE:Program from TABLE:Activities. The users can adjust those resources to fit their needs BUT is they select that activity again in that same record they lose all their changes and the resources are reset to the default values from the lookup.

[Paul de Halle]

Hi Carri

I would suggest using the Auto Enter Calculation function, with the option of 'Do not replace existing value of field' turned on. This will populate your field only once when the correct condition is met and never again, delivered the desired result i believe.

Cheers

Paul

[Lee Smith]

A Lookup will do what you describe. The help on lookups is pretty good, Lookup Help

However, I would use the Auto Enter by calculation, and deselect the button "Do not replace existing value of Field (if any) Auto Enter

HTH

Lee

[Lee Smith]

Sorry Paul, didn't mean to repeat what you posted, but I'll leave mind because it also points to the help section for more information on both types of entries.

Lee

[Carri]

Wow it's that simple ... thank you so much!

What if we found an error in the original value and needed all those activities to be "relooked up" how would I do that?

[Carri]

Thank you!

[Lee Smith]

There is a way, but it will effect every record.

Go into Define Fields, and change the text field to a calculation field. Close the Define Fields, and it will change the field data. Then reenter Define fields, and click on the options again. Select the Calculation, and the Okay, and Close the Define fields.

HTH

Lee

[color:red]p.s.

This is where the ReLookup might have a slight advantage, because you can work with a Found Set, or individual Record.

Edited March 2, 2008 by Guest
p.s.

[Carri]

Question about the change from lookup to auto-enter:

If data is already in the field that was calculated on entry (do not replace is checked off). And a user now wanted to use that same record but change the activity which is the field that the data is being calculated according to. Will it not replace the data of the old activity.

If not how do I word around that as I need it to change if the user selects a different activity as the default resouces are now different (ref. to origianl post for example)?

Thanks, Thanks and Thanks

[Lee Smith]

Easy enough to see for yourself. Make a test file, and have the auto enter calculation based on the entry of a couple of fields (i.e. Field1 + Field2)

With the option selected, change the data in one of the fields the calculation is based on.

Override the calculation, and then change the data in one of the fields that the calculation is based on.

Deselect the option, and then test it again.

Lee

Edited March 4, 2008 by Guest